[SCM] live-manual branch, debian-next, updated. debian/3.0_a11-1-73-gdd51eb2
chals
chals at altorricon.com
Sun Jun 3 18:51:30 UTC 2012
The following commit has been merged in the debian-next branch:
commit dd51eb2b1e2d9a0146ac2f66dfac34131c7e1dcc
Author: chals <chals at altorricon.com>
Date: Sun Jun 3 20:51:23 2012 +0200
Fixing fuzzy strings in 'es', 'fr' and 'it' after updating the persistence section.
diff --git a/manual/de/user_customization-runtime.ssi b/manual/de/user_customization-runtime.ssi
index 30b0b38..a5dc96b 100644
--- a/manual/de/user_customization-runtime.ssi
+++ b/manual/de/user_customization-runtime.ssi
@@ -130,7 +130,7 @@ other media in addition to CDs; but still, in its default behaviour, it
should be considered read-only and all the run-time evolutions of the system
are lost at shutdown.
-Persistence is a common name for different kinds of solutions for saving
+'Persistence' is a common name for different kinds of solutions for saving
across reboots some, or all, of this run-time evolution of the system. To
understand how it could work it could be handy to know that even if the
system is booted and run from read-only media, modification to the files and
@@ -141,11 +141,12 @@ The data stored on this ramdisk should be saved on a writable persistent
medium like local storage media, a network share or even a session of a
multisession (re)writable CD/DVD. All these media are supported in Debian
Live in different ways, and all but the last one require a special boot
-parameter to be specified at boot time: #{persistent}#.
+parameter to be specified at boot time: #{persistence}#.
-If the boot parameter #{persistent}# is set (and #{nopersistent}# is not
+If the boot parameter #{persistence}# is set (and #{nopersistence}# is not
set), local storage media (e.g. hard disks, USB drives) will be probed for
-persistent volumes during boot. A persistent volume is any of the following:
+persistence volumes during boot. A persistence volume is any of the
+following:
_* a partition, identified by its GPT name.
@@ -156,12 +157,12 @@ _* an image/archive file located on the root of any readable filesystem
this case the file name must also use the containing filesystem as the file
extension, e.g. "<label>.ext4".
-It is possible to restrict which types of persistent volumes to use by
+It is possible to restrict which types of persistence volumes to use by
specifying certain boot parameters described in the live-boot(7) man
page. The "identifying labels" referred to above can be any of the
following:
-_* #{full-ov}# for full persistent overlays.
+_* #{full-ov}# for full persistence overlays.
_* #{custom-ov}# for custom overlays.
@@ -169,11 +170,11 @@ _* #{live-sn}# for full system snapshots.
_* #{home-sn}# for /home snapshots.
-3~ Full persistent overlays
+3~ Full persistence overlays
By 'full persistence' it is meant that instead of using a tmpfs for storing
modifications to the read-only media (with the copy-on-write, COW, system) a
-persistent volume is used. For this type of persistence the volume label
+persistence volume is used. For this type of persistence the volume label
must be #{full-ov}#. This could, for instance, be an ext4 partition on a
hard disk or on a usb key created with, e.g.:
@@ -210,52 +211,53 @@ reboot.
3~ Custom overlays
A volume with the label #{custom-ov}# can be configured to make arbitrary
-directories persistent. The file #{live.persist}#, located on the volume's
-filesystem root, controls which directories it makes persistent, and in
-which way.
+directories persistent. The file #{live-persistence.conf}#, located on the
+volume's filesystem root, controls which directories it makes persistent,
+and in which way.
How custom overlay mounts are configured is described in full detail in the
-live.persist(5) man page, but a simple example should be sufficient for most
-uses. Let's say we want to make our home directory and APT cache persistent
-in an ext4 filesystem on the /dev/sdb1 partition:
+live-persistence.conf(5) man page, but a simple example should be sufficient
+for most uses. Let's say we want to make our home directory and APT cache
+persistent in an ext4 filesystem on the /dev/sdb1 partition:
code{
$ mkfs.ext4 -L custom-ov /dev/sdb1
$ mount -t ext4 /dev/sdb1 /mnt
- $ echo "/home" >> /mnt/live.persist
- $ echo "/var/cache/apt" >> /mnt/live.persist
+ $ echo "/home" >> /mnt/live-persistence.conf
+ $ echo "/var/cache/apt" >> /mnt/live-persistence.conf
}code
Then we reboot. During the first boot the contents of #{/home}# and
-#{/var/cache/apt}# will be copied into the persistent volume, and from then
-on all changes to these directories will live in the persistent
-volume. Please note that any paths listed in the #{live.persist}# file
-cannot contain white spaces or the special #{.}# and #{..}# path
+#{/var/cache/apt}# will be copied into the persistence volume, and from then
+on all changes to these directories will live in the persistence
+volume. Please note that any paths listed in the #{live-persistence.conf}#
+file cannot contain white spaces or the special #{.}# and #{..}# path
components. Also, neither #{/live}# (or any of its sub-directories) nor
#{/}# can be made persistent using custom mounts (for the latter, use the
#{full-ov}# type persistence described above).
-Several different custom overlay volumes (with their own #{live.persist}#
-files) can be used at the same time, but if several volumes make the same
-directory persistent, only one of them will be used. If any two mounts are
-"nested" (i.e. one is a sub-directory of the other) the parent will be
-mounted before the child so no mount will be hidden by the other. Nested
-custom mounts are problematic if they are listed in the same
-#{live.persist}# file. See the live.persist(5) man page for how to handle
-that case if you really need it (hint: you usually don't).
+Several different custom overlay volumes (with their own
+#{live-persistence.conf}# files) can be used at the same time, but if
+several volumes make the same directory persistent, only one of them will be
+used. If any two mounts are "nested" (i.e. one is a sub-directory of the
+other) the parent will be mounted before the child so no mount will be
+hidden by the other. Nested custom mounts are problematic if they are listed
+in the same #{live-persistence.conf}# file. See the live-persistence.conf(5)
+man page for how to handle that case if you really need it (hint: you
+usually don't).
3~ Snapshots
Snapshots are collections of files and directories which are not mounted
-while running but which are copied from a persistent volume to the system
+while running but which are copied from a persistence volume to the system
(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The
volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive
named #{live-sn.cpio.gz}#. A power interruption during run time could lead
to data loss, hence, if you have important changes, invoke #{live-snapshot
--refresh}# as often as needed. This type of persistence, since it does not
-write continuously to the persistent media, is the most flash-based device
+write continuously to the persistence media, is the most flash-based device
friendly and the fastest of all the persistence systems, but it occupies as
much RAM as the size of the uncompressed snapshot.
@@ -264,15 +266,15 @@ works the same as the main snapshot but it is only applied to /home.
Snapshots cannot currently handle file deletion.
-3~ Persistent SubText
+3~ Persistence SubText
-If a user would need multiple persistent storage of the same type for
+If a user would need multiple persistence storage of the same type for
different locations or testing, such as #{full-ov-nonwork}# and
-#{full-ov-work}#, the boot parameter #{persistent-subtext}# used in
-conjunction with the boot parameter #{persistent}# will allow for multiple
-but unique persistent media. An example would be if a user wanted to use a
-persistent partition labeled #{live-sn-subText}# they would use the boot
-parameters of: #{persistent}# #{persistent-subtext=subText}#.
+#{full-ov-work}#, the boot parameter #{persistence-subtext}# used in
+conjunction with the boot parameter #{persistence}# will allow for multiple
+but unique persistence media. An example would be if a user wanted to use a
+persistence partition labeled #{live-sn-subText}# they would use the boot
+parameters of: #{persistence}# #{persistence-subtext=subText}#.
3~ Partial remastering
diff --git a/manual/es/user_customization-runtime.ssi b/manual/es/user_customization-runtime.ssi
index 515b1e2..a0d312c 100644
--- a/manual/es/user_customization-runtime.ssi
+++ b/manual/es/user_customization-runtime.ssi
@@ -142,7 +142,7 @@ su comportamiento predeterminado, se debe considerar un sistema de sólo
lectura y todos los cambios en tiempo de ejecución del sistema se pierden al
apagar el equipo.
-La persistencia es un nombre común que se da a los diferentes tipos de
+La «persistencia» es un nombre común que se da a los diferentes tipos de
soluciones para guardar algunos o todos los cambios realizados durante la
ejecución tras reiniciar el sistema. Para entender cómo funciona es útil
saber que incluso si el sistema se inicia y se ejecuta desde los medios de
@@ -151,14 +151,14 @@ directorios se escriben en medios de escritura, por lo general en la memoria
ram (tmpfs) y los datos guardados en la ram no se guardan tras reiniciar.
Los datos almacenados en esta memoria ram se pueden guardar en un soporte
-grabable como un medio de almacenamiento local, un recurso compartido en red
-o incluso en una sesión de un CD/DVD regrabable en multisesión. Todos estos
-medios son compatibles con Debian Live de diferentes maneras, y todos menos
-el último requieren un parámetro de arranque especial que se especificará en
-el momento del arranque: #{persistent}#.
-
-Si se usa el parámetro de arranque #{persistent}# (y no se usa la opción
-#{nopersistent}#), se busca en los medios de almacenamiento locales
+grabable, como un medio de almacenamiento local, un recurso compartido en
+red o incluso en una sesión de un CD/DVD regrabable en multisesión. Todos
+estos medios son compatibles con Debian Live de diferentes maneras y todos,
+menos el último, requieren un parámetro de arranque especial que se
+especificará en el momento del arranque: #{persistence}#.
+
+Si se usa el parámetro de arranque #{persistence}# (y no se usa la opción
+#{nopersistence}#), se busca en los medios de almacenamiento locales
(p.ej. discos duros, llaves USB) volúmenes con persistencia durante el
arranque. Un volumen persistente es cualquiera de los siguientes:
@@ -229,44 +229,44 @@ reiniciar el sistema.
3~ Capas personalizadas
Un volumen con la etiqueta #{custom-ov}# puede ser personalizado para crear
-arbitrariamente directorios persistentes. El fichero #{live.persist}#,
-situado en el sistema de ficheros raiz del volumen, controla que directorios
-hace persistentes y también de que manera.
+arbitrariamente directorios persistentes. El fichero
+#{live-persistence.conf}#, situado en el sistema de ficheros raiz del
+volumen, controla que directorios hace persistentes y también de que manera.
-En la página de manual de live.persist(5) se explica en detalle cómo se
-configura el montaje de las capas, pero un sencillo ejemplo es suficiente
-para la mayoría de los casos. Supongamos que queremos crear nuestro
-directorio home y APT cache persistentes en un sistema de ficheros ext4 en
-la partición /dev/sdb1:
+En la página de manual de live-persistence.conf(5) se explica en detalle
+cómo se configura el montaje de las capas, pero un sencillo ejemplo es
+suficiente para la mayoría de los casos. Supongamos que queremos crear
+nuestro directorio home y APT cache persistentes en un sistema de ficheros
+ext4 en la partición /dev/sdb1:
code{
$ mkfs.ext4 -L custom-ov /dev/sdb1
$ mount -t ext4 /dev/sdb1 /mnt
- $ echo "/home" >> /mnt/live.persist
- $ echo "/var/cache/apt" >> /mnt/live.persist
+ $ echo "/home" >> /mnt/live-persistence.conf
+ $ echo "/var/cache/apt" >> /mnt/live-persistence.conf
}code
Entonces reiniciamos. Durante el primer arranque los contenidos de #{/home}#
y #{/var/cache/apt}# se copiarán en el volumen persistente y a partir de ese
momento todos los cambios en esos directorios se guardarán allí. Tener en
-cuenta que los rutas listadas en el fichero #{live.persist}# no pueden
-contener espacios en blanco ni los componentes especiales #{.}# y
-#{..}#. Además ni #{/live}# (o ninguno de sus sub-directorios) ni #{/}#
-pueden hacerse persistentes montándolos de forma personalizada. Para este
+cuenta que las rutas listadas en el fichero #{live-persistence.conf}# no
+pueden contener espacios en blanco ni los componentes especiales #{.}# y
+#{..}#. Además, ni #{/live}# (o ninguno de sus sub-directorios) ni #{/}#
+pueden hacerse persistentes montándolos de forma personalizada. Para esto
último, usar el tipo de persistencia #{full-ov}# descrito anteriormente.
Se puede usar diferentes volúmenes de capas personalizados al mismo tiempo
-(con sus propios ficheros #{live.persist}#) pero si varios volúmenes hacen
-que un mismo directorio sea persistente, sólo uno de ellos será usado. Si
-dos unidades montadas están "anidadas" (es decir, una es un sub-directorio
-de la otra) el directorio superior será montado antes que el inferior de
-este modo no quedará uno escondido por el otro. La personalización de los
-montajes anidadados es problemática si están listados en el mismo fichero
-#{live.persist}#. Consultar la página de manual de live.persist(5) para ver
-como manejar ese caso si realmente es necesario. (aclaración: normalmente no
-lo es).
+(con sus propios ficheros #{live-persistence.conf}#) pero si varios
+volúmenes hacen que un mismo directorio sea persistente, sólo uno de ellos
+será usado. Si dos unidades montadas están "anidadas" (es decir, una es un
+sub-directorio de la otra) el directorio superior será montado antes que el
+inferior de este modo no quedará uno escondido por el otro. La
+personalización de los montajes anidadados es problemática si están listados
+en el mismo fichero #{live-persistence.conf}#. Consultar la página de manual
+de live-persistence.conf(5) para ver como manejar ese caso si realmente es
+necesario. (aclaración: normalmente no lo es).
3~ Instantáneas
@@ -293,12 +293,12 @@ Las instantáneas no pueden manejar el borrado de ficheros.
Si un usuario necesita un almacenamiento persistente múltiple del mismo tipo
para diferentes lugares o pruebas, tales como #{full-ov-nonwork}# y
-#{full-ov-work}#, el parámetro de arranque #{persistent-subtext}# usado
-junto con el parámetro de arranque #{persistent}# permitirá medios de
+#{full-ov-work}#, el parámetro de arranque #{persistence-subtext}# usado
+junto con el parámetro de arranque #{persistence}# permitirá medios de
almacenamiento persistentes múltiples pero únicos. Un ejemplo sería, si un
usuario desea utilizar una partición persistente etiquetada
-#{live-sn-subText}# usaría los parámetros de arranque: #{persistent}#
-#{persistent-subtext=subText}#.
+#{live-sn-subText}# usaría los parámetros de arranque: #{persistence}#
+#{persistence-subtext=subText}#.
3~ Remasterización parcial
diff --git a/manual/fr/user_customization-runtime.ssi b/manual/fr/user_customization-runtime.ssi
index b45bb29..9250394 100644
--- a/manual/fr/user_customization-runtime.ssi
+++ b/manual/fr/user_customization-runtime.ssi
@@ -140,8 +140,8 @@ ainsi autres supports, en plus de CDs, mais encore, dans son comportement
par défaut, il doit être considéré en lecture seule et toutes les évolutions
pendant l'exécution du système sont perdus à l'arrêt.
-La persistance est un nom commun pour les différents types de solutions pour
-sauver, après un redémarrage, certaines ou toutes les données, de cette
+La «persistance» est un nom commun pour les différents types de solutions
+pour sauver, après un redémarrage, certaines ou toutes les données, de cette
évolution pendant l'exécution du système. Pour comprendre comment cela
pourrait fonctionner il pourrait être utile de savoir que même si le système
est démarré et exécuté à partir d'un support en lecture seule, la
@@ -154,9 +154,9 @@ support inscriptible persistant comme supports de stockage locaux, un
partage réseau ou même une séance d'un CD/DVD multisession
(ré)inscriptible. Tous ces supports sont pris en charge dans Debian Live de
différentes manières, et tous, moins le dernier, nécessitent un paramètre
-d'amorçage spéciale à préciser au moment du démarrage: #{persistent}#.
+d'amorçage spéciale à préciser au moment du démarrage: #{persistence}#.
-Si le paramètre de démarrage #{persistent}# est réglé (et #{nopersistent}#
+Si le paramètre de démarrage #{persistence}# est réglé (et #{nopersistence}#
n'est pas utilisé), les supports de stockage locaux (par exemple les disques
durs, clés USB) seront examinés pour trouver des volumes persistants pendant
le démarrage. Un volume persistant est un des éléments suivants:
@@ -228,22 +228,22 @@ Ensuite, copiez le fichier #{full-ov}# sur une partition accessible en
3~ Couches personnalisées
Un volume avec l'étiquette #{custom-ov}# peut être configuré pour créer des
-répertoires persistants arbitraires. Le fichier #{live.persist}#, situé sur
-le système de fichiers racine du volume, contrôle quels répertoires il fait
-persistants, et de quelle manière.
+répertoires persistants arbitraires. Le fichier #{live-persistence.conf}#,
+situé sur le système de fichiers racine du volume, contrôle quels
+répertoires il fait persistants, et de quelle manière.
Comment on configure monter des couches personnalisées est décrit en détail
-dans la page de manuel live.persist(5), mais un simple exemple devrait être
-suffisant pour la plupart des utilisations. Imaginons que nous voulons faire
-notre répertoire personnel et APT cache persistants dans un système de
-fichiers ext4 sur la partition /dev/sdb1:
+dans la page de manuel live-persistence.conf(5), mais un simple exemple
+devrait être suffisant pour la plupart des utilisations. Imaginons que nous
+voulons faire notre répertoire personnel et APT cache persistants dans un
+système de fichiers ext4 sur la partition /dev/sdb1:
code{
$ mkfs.ext4 -L custom-ov /dev/sdb1
$ mount -t ext4 /dev/sdb1 /mnt
- $ echo "/home" >> /mnt/live.persist
- $ echo "/var/cache/apt" >> /mnt/live.persist
+ $ echo "/home" >> /mnt/live-persistence.conf
+ $ echo "/var/cache/apt" >> /mnt/live-persistence.conf
}code
@@ -251,22 +251,22 @@ Alors nous redémarrons. Lors du premier démarrage les contenus du #{/home}#
et #{/var/cache/apt}# seront copiés dans le volume persistant, et à partir
de ce moment tous les changements dans ces répertoires seront stockés dans
le volume persistant. S'il vous plaît souligner que les chemins d'accès aux
-répertoriés dans le fichier #{live.persist}# ne peuvent pas contenir
-d'espaces blancs ou les éléments spéciaux #{.}# et #{..}#. En outre, ni
-#{/live}# (ou un de ses sous-répertoires), ni #{/}# peuvent être rendus
-persistants en utilisant custom mounts (pour ce dernier, utilisez la
+répertoriés dans le fichier #{live-persistence.conf}# ne peuvent pas
+contenir d'espaces blancs ou les éléments spéciaux #{.}# et #{..}#. En
+outre, ni #{/live}# (ou un de ses sous-répertoires), ni #{/}# peuvent être
+rendus persistants en utilisant custom mounts (pour ce dernier, utilisez la
persistance #{full-ov}# décrite ci-dessus).
Plusieurs volumes de couches personnalisées différents (avec leurs propres
-fichiers #{live.persist}#) peuvent être utilisées au même temps, mais si
-plusieurs volumes font le même répertoire persistant, un seul d'entre eux
-sera utilisé. Si les deux sont «imbriqués» (un est un sous-répertoire de
-l'autre) le premier sera monté avant que le secondaire de sorte que aucun
-sera caché par l'autre. Monter des éléments personnalisés imbriqués est
-problématique s'ils sont énumérés dans le même fichier
-#{live.persist}#. Voir la page de manuel live.persist(5) pour savoir comment
-gérer ce cas, si vous avez vraiment besoin (remarque: vous n'avez
-généralement pas).
+fichiers #{live-persistence.conf}#) peuvent être utilisées au même temps,
+mais si plusieurs volumes font le même répertoire persistant, un seul
+d'entre eux sera utilisé. Si les deux sont «imbriqués» (un est un
+sous-répertoire de l'autre) le premier sera monté avant que le secondaire de
+sorte que aucun sera caché par l'autre. Monter des éléments personnalisés
+imbriqués est problématique s'ils sont énumérés dans le même fichier
+#{live-persistence.conf}#. Voir la page de manuel live-persistence.conf(5)
+pour savoir comment gérer ce cas, si vous avez vraiment besoin (remarque:
+vous n'avez généralement pas).
3~ Instantanés
@@ -294,12 +294,12 @@ fichiers.
Si un utilisateur a besoin de stockages persistants multiples du même type
pour différents endroits ou l'essai, tel que #{full-ov-nonwork}# et
-#{full-ov-work}#, le paramètre de démarrage #{persistent-subtext}# utilisé
-en conjonction avec le paramètre de démarrage #{persistent}# permettra
+#{full-ov-work}#, le paramètre de démarrage #{persistence-subtext}# utilisé
+en conjonction avec le paramètre de démarrage #{persistence}# permettra
multiples, mais uniques, supports persistants. Un exemple serait le cas si
un utilisateur voudrait utiliser une partition persistante étiquetée
#{live-sn-subText}# il utiliserait les paramètres de démarrage:
-#{persistent}# #{persistent-subtext=subText}#.
+#{persistence}# #{persistence-subtext=subText}#.
3~ Remasterisation partielle
diff --git a/manual/it/user_customization-runtime.ssi b/manual/it/user_customization-runtime.ssi
index 70046ae..e7b9ad4 100644
--- a/manual/it/user_customization-runtime.ssi
+++ b/manual/it/user_customization-runtime.ssi
@@ -145,10 +145,10 @@ scrivibile persistente come un supporto di memorizzazione locale, una
condivisione di rete o anche una sessione di un CD/DVD riscrivibile
multisessione. Tutti questi supporti sono gestiti in Debian Live in modi
differenti, e tutti tranne l'ultimo richiedono un parametro d'avvio speciale
-da specificare all'avvio: #{persistent}#.
+da specificare all'avvio: #{persistence}#.
-Se il parametro di boot #{persistent}# è impostato (e non lo è
-#{nopersistent}#), i supporti di memorizzazione locali (hard disk,
+Se il parametro di boot #{persistence}# è impostato (e non lo è
+#{nopersistence}#), i supporti di memorizzazione locali (hard disk,
dispositivi USB) saranno rilevati come volumi persistenti durante
l'avvio. Un volume persistente è uno dei seguenti:
@@ -217,12 +217,12 @@ scrivibile e riavviare.
3~ Strati personalizzati
Un volume con una label #{custom-ov}# può essere configurato per creare
-directory persistenti arbitrarie. Il file #{live.persist}#, situato nella
-directory radice del filesystem del volume, controlla quali rendere
+directory persistenti arbitrarie. Il file #{live-persistence.conf}#, situato
+nella directory radice del filesystem del volume, controlla quali rendere
persistenti e in che modo.
-Nella manpage di live.persist(5) è descritto dettagliatamente come è
-configurato il mount degli strati personalizzati, ma un semplice esempio
+Nella manpage di live-persistence.conf(5) è descritto dettagliatamente come
+è configurato il mount degli strati personalizzati, ma un semplice esempio
dovrebbe essere sufficiente per la maggior parte degli usi. Supponendo di
voler creare la directory home e quella della cache di APT in modo
persistente in un filesystem ext4 sulla partizione /dev/sdb1:
@@ -231,8 +231,8 @@ code{
$ mkfs.ext4 -L custom-ov /dev/sdb1
$ mount -t ext4 /dev/sdb1 /mnt
- $ echo "/home" >> /mnt/live.persist
- $ echo "/var/cache/apt" >> /mnt/live.persist
+ $ echo "/home" >> /mnt/live-persistence.conf
+ $ echo "/var/cache/apt" >> /mnt/live-persistence.conf
}code
@@ -240,20 +240,20 @@ Quindi riavviare. Durante il primo avvio il contenuto di #{/home}# e
#{/var/cache/apt}# saranno copiati nel volume persistente e da allora tutte
le modifiche a queste directory risiederanno in modo persistente sul
volume. C'è da considerare che tutti i path elencati nel file
-#{live.persist}# non possono contenere spazi o i caratteri speciali #{.}# e
-#{..}#; inoltre, né #{/live}# (o nessuna delle sue sottodirectory) né #{/}#
-può essere resa persistente tramite i mount personalizzati (per l'ultimo
-usare la tipologia #{full-ov}# descritta prima).
+#{live-persistence.conf}# non possono contenere spazi o i caratteri speciali
+#{.}# e #{..}#; inoltre, né #{/live}# (o nessuna delle sue sottodirectory)
+né #{/}# può essere resa persistente tramite i mount personalizzati (per
+l'ultimo usare la tipologia #{full-ov}# descritta prima).
Possono essere utilizzati svariati volumi di stratificazione personalizzati
-(con i rispettivi file #{live.persist}#) allo stesso tempo ma se questi
-creano la stessa directory persistente, ne verrà usata solo una. Se due
-directory montate sono "nidificate" (una è la sottodirectory dell'altra), la
-superiore sarà montata per prima, per cui nessuna operazione di mount verrà
-sovrastata dall'altra. I mount nidificati personalizzati sono problematici
-se sono elencati nello stesso file #{live.persist}. Se si ha davvero la
-necessità (in genere non si dovrebbe averla), consultare la manpage di
-live.persist(5) per sapere come gestire questo caso.
+(con i rispettivi file #{live-persistence.conf}#) allo stesso tempo ma se
+questi creano la stessa directory persistente, ne verrà usata solo una. Se
+due directory montate sono "nidificate" (una è la sottodirectory
+dell'altra), la superiore sarà montata per prima, per cui nessuna operazione
+di mount verrà sovrastata dall'altra. I mount nidificati personalizzati sono
+problematici se sono elencati nello stesso file #{live-persistence.conf}. Se
+si ha davvero la necessità (in genere non si dovrebbe averla), consultare la
+manpage di live-persistence.conf(5) per sapere come gestire questo caso.
3~ Istantanee
@@ -278,11 +278,11 @@ Attualmente le istantanee non possono gestire la cancellazione dei file.
Se un utente avesse bisogno di archiviazioni multiple dello stesso tipo per
differenti posti o per test, come #{full-ov-casa}# e #{full-ov-lavoro}#, il
-parametro d'avvio #{persistent-subtext}# usato in congiunzione con
+parametro d'avvio #{persistence-subtext}# usato in congiunzione con
#{persistent}# permetterà supporti persistenti multipli ma univoci. Un
esempio potrebbe essere un utente che vuole usare una partizione etichettata
-come #{live-sn-sottotesto}#, userebbe: #{persistent}#
-#{persistent-subtext=sottotesto}#.
+come #{live-sn-sottotesto}#, userebbe: #{persistence}#
+#{persistence-subtext=sottotesto}#.
3~ Rimasterizzazione parziale
diff --git a/manual/po/de/user_customization-runtime.ssi.po b/manual/po/de/user_customization-runtime.ssi.po
index d72612b..5ab405a 100644
--- a/manual/po/de/user_customization-runtime.ssi.po
+++ b/manual/po/de/user_customization-runtime.ssi.po
@@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-04-08 12:15+0300\n"
+"POT-Creation-Date: 2012-06-03 20:02+0300\n"
"PO-Revision-Date: 2011-04-23 14:15+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -16,11 +16,10 @@ msgstr ""
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. type: Plain text
-#: en/about_manual.ssi:90 en/about_manual.ssi:98 en/about_manual.ssi:106
-#: en/about_manual.ssi:114 en/about_manual.ssi:122 en/about_manual.ssi:130
-#: en/about_manual.ssi:142 en/about_manual.ssi:155 en/about_manual.ssi:168
-#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/about_manual.ssi:195
-#: en/about_manual.ssi:203 en/project_bugs.ssi:60
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:140 en/about_manual.ssi:153 en/about_manual.ssi:166
+#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:30 en/project_coding-style.ssi:40
#: en/project_coding-style.ssi:53 en/project_coding-style.ssi:63
#: en/project_coding-style.ssi:94 en/project_coding-style.ssi:102
@@ -87,11 +86,10 @@ msgid "code{"
msgstr ""
#. type: Plain text
-#: en/about_manual.ssi:94 en/about_manual.ssi:102 en/about_manual.ssi:110
-#: en/about_manual.ssi:118 en/about_manual.ssi:126 en/about_manual.ssi:134
-#: en/about_manual.ssi:151 en/about_manual.ssi:164 en/about_manual.ssi:173
-#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/about_manual.ssi:199
-#: en/about_manual.ssi:207 en/project_bugs.ssi:64
+#: en/about_manual.ssi:92 en/about_manual.ssi:100 en/about_manual.ssi:108
+#: en/about_manual.ssi:116 en/about_manual.ssi:124 en/about_manual.ssi:132
+#: en/about_manual.ssi:149 en/about_manual.ssi:162 en/about_manual.ssi:171
+#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:36 en/project_coding-style.ssi:47
#: en/project_coding-style.ssi:59 en/project_coding-style.ssi:70
#: en/project_coding-style.ssi:98 en/project_coding-style.ssi:106
@@ -377,7 +375,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:96
msgid ""
-"Persistence is a common name for different kinds of solutions for saving "
+"'Persistence' is a common name for different kinds of solutions for saving "
"across reboots some, or all, of this run-time evolution of the system. To "
"understand how it could work it could be handy to know that even if the "
"system is booted and run from read-only media, modification to the files and "
@@ -392,15 +390,16 @@ msgid ""
"medium like local storage media, a network share or even a session of a "
"multisession (re)writable CD/DVD. All these media are supported in Debian "
"Live in different ways, and all but the last one require a special boot "
-"parameter to be specified at boot time: #{persistent}#."
+"parameter to be specified at boot time: #{persistence}#."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:100
msgid ""
-"If the boot parameter #{persistent}# is set (and #{nopersistent}# is not "
+"If the boot parameter #{persistence}# is set (and #{nopersistence}# is not "
"set), local storage media (e.g. hard disks, USB drives) will be probed for "
-"persistent volumes during boot. A persistent volume is any of the following:"
+"persistence volumes during boot. A persistence volume is any of the "
+"following:"
msgstr ""
#. type: Plain text
@@ -425,14 +424,14 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:108
msgid ""
-"It is possible to restrict which types of persistent volumes to use by "
+"It is possible to restrict which types of persistence volumes to use by "
"specifying certain boot parameters described in the live-boot(7) man page. "
"The \"identifying labels\" referred to above can be any of the following:"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:110
-msgid "_* #{full-ov}# for full persistent overlays."
+msgid "_* #{full-ov}# for full persistence overlays."
msgstr ""
#. type: Plain text
@@ -452,7 +451,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:118
-msgid "3~ Full persistent overlays"
+msgid "3~ Full persistence overlays"
msgstr ""
#. type: Plain text
@@ -460,7 +459,7 @@ msgstr ""
msgid ""
"By 'full persistence' it is meant that instead of using a tmpfs for storing "
"modifications to the read-only media (with the copy-on-write, COW, system) a "
-"persistent volume is used. For this type of persistence the volume label "
+"persistence volume is used. For this type of persistence the volume label "
"must be #{full-ov}#. This could, for instance, be an ext4 partition on a "
"hard disk or on a usb key created with, e.g.:"
msgstr ""
@@ -520,18 +519,18 @@ msgstr ""
#: en/user_customization-runtime.ssi:151
msgid ""
"A volume with the label #{custom-ov}# can be configured to make arbitrary "
-"directories persistent. The file #{live.persist}#, located on the volume's "
-"filesystem root, controls which directories it makes persistent, and in "
-"which way."
+"directories persistent. The file #{live-persistence.conf}#, located on the "
+"volume's filesystem root, controls which directories it makes persistent, "
+"and in which way."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:153
msgid ""
"How custom overlay mounts are configured is described in full detail in the "
-"live.persist(5) man page, but a simple example should be sufficient for most "
-"uses. Let's say we want to make our home directory and APT cache persistent "
-"in an ext4 filesystem on the /dev/sdb1 partition:"
+"live-persistence.conf(5) man page, but a simple example should be sufficient "
+"for most uses. Let's say we want to make our home directory and APT cache "
+"persistent in an ext4 filesystem on the /dev/sdb1 partition:"
msgstr ""
#. type: Plain text
@@ -540,34 +539,34 @@ msgstr ""
msgid ""
" $ mkfs.ext4 -L custom-ov /dev/sdb1\n"
" $ mount -t ext4 /dev/sdb1 /mnt\n"
-" $ echo \"/home\" >> /mnt/live.persist\n"
-" $ echo \"/var/cache/apt\" >> /mnt/live.persist\n"
+" $ echo \"/home\" >> /mnt/live-persistence.conf\n"
+" $ echo \"/var/cache/apt\" >> /mnt/live-persistence.conf\n"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:164
msgid ""
"Then we reboot. During the first boot the contents of #{/home}# and #{/var/"
-"cache/apt}# will be copied into the persistent volume, and from then on all "
-"changes to these directories will live in the persistent volume. Please note "
-"that any paths listed in the #{live.persist}# file cannot contain white "
-"spaces or the special #{.}# and #{..}# path components. Also, neither #{/"
-"live}# (or any of its sub-directories) nor #{/}# can be made persistent "
-"using custom mounts (for the latter, use the #{full-ov}# type persistence "
-"described above)."
+"cache/apt}# will be copied into the persistence volume, and from then on all "
+"changes to these directories will live in the persistence volume. Please "
+"note that any paths listed in the #{live-persistence.conf}# file cannot "
+"contain white spaces or the special #{.}# and #{..}# path components. Also, "
+"neither #{/live}# (or any of its sub-directories) nor #{/}# can be made "
+"persistent using custom mounts (for the latter, use the #{full-ov}# type "
+"persistence described above)."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:166
msgid ""
-"Several different custom overlay volumes (with their own #{live.persist}# "
-"files) can be used at the same time, but if several volumes make the same "
-"directory persistent, only one of them will be used. If any two mounts are "
-"\"nested\" (i.e. one is a sub-directory of the other) the parent will be "
+"Several different custom overlay volumes (with their own #{live-persistence."
+"conf}# files) can be used at the same time, but if several volumes make the "
+"same directory persistent, only one of them will be used. If any two mounts "
+"are \"nested\" (i.e. one is a sub-directory of the other) the parent will be "
"mounted before the child so no mount will be hidden by the other. Nested "
-"custom mounts are problematic if they are listed in the same #{live.persist}"
-"# file. See the live.persist(5) man page for how to handle that case if you "
-"really need it (hint: you usually don't)."
+"custom mounts are problematic if they are listed in the same #{live-"
+"persistence.conf}# file. See the live-persistence.conf(5) man page for how "
+"to handle that case if you really need it (hint: you usually don't)."
msgstr ""
#. type: Plain text
@@ -579,13 +578,13 @@ msgstr ""
#: en/user_customization-runtime.ssi:170
msgid ""
"Snapshots are collections of files and directories which are not mounted "
-"while running but which are copied from a persistent volume to the system "
+"while running but which are copied from a persistence volume to the system "
"(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The "
"volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive "
"named #{live-sn.cpio.gz}#. A power interruption during run time could lead "
"to data loss, hence, if you have important changes, invoke #{live-snapshot --"
"refresh}# as often as needed. This type of persistence, since it does not "
-"write continuously to the persistent media, is the most flash-based device "
+"write continuously to the persistence media, is the most flash-based device "
"friendly and the fastest of all the persistence systems, but it occupies as "
"much RAM as the size of the uncompressed snapshot."
msgstr ""
@@ -604,19 +603,19 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:176
-msgid "3~ Persistent SubText"
+msgid "3~ Persistence SubText"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:178
msgid ""
-"If a user would need multiple persistent storage of the same type for "
+"If a user would need multiple persistence storage of the same type for "
"different locations or testing, such as #{full-ov-nonwork}# and #{full-ov-"
-"work}#, the boot parameter #{persistent-subtext}# used in conjunction with "
-"the boot parameter #{persistent}# will allow for multiple but unique "
-"persistent media. An example would be if a user wanted to use a persistent "
+"work}#, the boot parameter #{persistence-subtext}# used in conjunction with "
+"the boot parameter #{persistence}# will allow for multiple but unique "
+"persistence media. An example would be if a user wanted to use a persistence "
"partition labeled #{live-sn-subText}# they would use the boot parameters of: "
-"#{persistent}# #{persistent-subtext=subText}#."
+"#{persistence}# #{persistence-subtext=subText}#."
msgstr ""
#. type: Plain text
diff --git a/manual/po/es/user_customization-runtime.ssi.po b/manual/po/es/user_customization-runtime.ssi.po
index 626ad5e..d7ed337 100644
--- a/manual/po/es/user_customization-runtime.ssi.po
+++ b/manual/po/es/user_customization-runtime.ssi.po
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-04-08 12:15+0300\n"
+"POT-Creation-Date: 2012-06-03 20:02+0300\n"
"PO-Revision-Date: 2012-03-24 13:18+0100\n"
"Last-Translator: José Luis Zabalza and Carlos Zuferri «chals» "
"<jlz.3008 at gmail.com> <chals at altorricon.com>\n"
@@ -21,11 +21,10 @@ msgstr ""
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. type: Plain text
-#: en/about_manual.ssi:90 en/about_manual.ssi:98 en/about_manual.ssi:106
-#: en/about_manual.ssi:114 en/about_manual.ssi:122 en/about_manual.ssi:130
-#: en/about_manual.ssi:142 en/about_manual.ssi:155 en/about_manual.ssi:168
-#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/about_manual.ssi:195
-#: en/about_manual.ssi:203 en/project_bugs.ssi:60
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:140 en/about_manual.ssi:153 en/about_manual.ssi:166
+#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:30 en/project_coding-style.ssi:40
#: en/project_coding-style.ssi:53 en/project_coding-style.ssi:63
#: en/project_coding-style.ssi:94 en/project_coding-style.ssi:102
@@ -92,11 +91,10 @@ msgid "code{"
msgstr "code{"
#. type: Plain text
-#: en/about_manual.ssi:94 en/about_manual.ssi:102 en/about_manual.ssi:110
-#: en/about_manual.ssi:118 en/about_manual.ssi:126 en/about_manual.ssi:134
-#: en/about_manual.ssi:151 en/about_manual.ssi:164 en/about_manual.ssi:173
-#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/about_manual.ssi:199
-#: en/about_manual.ssi:207 en/project_bugs.ssi:64
+#: en/about_manual.ssi:92 en/about_manual.ssi:100 en/about_manual.ssi:108
+#: en/about_manual.ssi:116 en/about_manual.ssi:124 en/about_manual.ssi:132
+#: en/about_manual.ssi:149 en/about_manual.ssi:162 en/about_manual.ssi:171
+#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:36 en/project_coding-style.ssi:47
#: en/project_coding-style.ssi:59 en/project_coding-style.ssi:70
#: en/project_coding-style.ssi:98 en/project_coding-style.ssi:106
@@ -449,14 +447,14 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:96
msgid ""
-"Persistence is a common name for different kinds of solutions for saving "
+"'Persistence' is a common name for different kinds of solutions for saving "
"across reboots some, or all, of this run-time evolution of the system. To "
"understand how it could work it could be handy to know that even if the "
"system is booted and run from read-only media, modification to the files and "
"directories are written on writable media, typically a ram disk (tmpfs) and "
"ram disks' data do not survive reboots."
msgstr ""
-"La persistencia es un nombre común que se da a los diferentes tipos de "
+"La «persistencia» es un nombre común que se da a los diferentes tipos de "
"soluciones para guardar algunos o todos los cambios realizados durante la "
"ejecución tras reiniciar el sistema. Para entender cómo funciona es útil "
"saber que incluso si el sistema se inicia y se ejecuta desde los medios de "
@@ -471,24 +469,25 @@ msgid ""
"medium like local storage media, a network share or even a session of a "
"multisession (re)writable CD/DVD. All these media are supported in Debian "
"Live in different ways, and all but the last one require a special boot "
-"parameter to be specified at boot time: #{persistent}#."
+"parameter to be specified at boot time: #{persistence}#."
msgstr ""
"Los datos almacenados en esta memoria ram se pueden guardar en un soporte "
-"grabable como un medio de almacenamiento local, un recurso compartido en red "
-"o incluso en una sesión de un CD/DVD regrabable en multisesión. Todos estos "
-"medios son compatibles con Debian Live de diferentes maneras, y todos menos "
-"el último requieren un parámetro de arranque especial que se especificará en "
-"el momento del arranque: #{persistent}#."
+"grabable, como un medio de almacenamiento local, un recurso compartido en "
+"red o incluso en una sesión de un CD/DVD regrabable en multisesión. Todos "
+"estos medios son compatibles con Debian Live de diferentes maneras y todos, "
+"menos el último, requieren un parámetro de arranque especial que se "
+"especificará en el momento del arranque: #{persistence}#."
#. type: Plain text
#: en/user_customization-runtime.ssi:100
msgid ""
-"If the boot parameter #{persistent}# is set (and #{nopersistent}# is not "
+"If the boot parameter #{persistence}# is set (and #{nopersistence}# is not "
"set), local storage media (e.g. hard disks, USB drives) will be probed for "
-"persistent volumes during boot. A persistent volume is any of the following:"
+"persistence volumes during boot. A persistence volume is any of the "
+"following:"
msgstr ""
-"Si se usa el parámetro de arranque #{persistent}# (y no se usa la opción #"
-"{nopersistent}#), se busca en los medios de almacenamiento locales (p.ej. "
+"Si se usa el parámetro de arranque #{persistence}# (y no se usa la opción #"
+"{nopersistence}#), se busca en los medios de almacenamiento locales (p.ej. "
"discos duros, llaves USB) volúmenes con persistencia durante el arranque. Un "
"volumen persistente es cualquiera de los siguientes: "
@@ -521,7 +520,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:108
msgid ""
-"It is possible to restrict which types of persistent volumes to use by "
+"It is possible to restrict which types of persistence volumes to use by "
"specifying certain boot parameters described in the live-boot(7) man page. "
"The \"identifying labels\" referred to above can be any of the following:"
msgstr ""
@@ -532,7 +531,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:110
-msgid "_* #{full-ov}# for full persistent overlays."
+msgid "_* #{full-ov}# for full persistence overlays."
msgstr "_* #{full-ov}# para capas de persistencia total."
#. type: Plain text
@@ -552,7 +551,7 @@ msgstr "_* #{home-sn}# para instantáneas de /home."
#. type: Plain text
#: en/user_customization-runtime.ssi:118
-msgid "3~ Full persistent overlays"
+msgid "3~ Full persistence overlays"
msgstr "3~ Capas de persistencia total "
#. type: Plain text
@@ -560,7 +559,7 @@ msgstr "3~ Capas de persistencia total "
msgid ""
"By 'full persistence' it is meant that instead of using a tmpfs for storing "
"modifications to the read-only media (with the copy-on-write, COW, system) a "
-"persistent volume is used. For this type of persistence the volume label "
+"persistence volume is used. For this type of persistence the volume label "
"must be #{full-ov}#. This could, for instance, be an ext4 partition on a "
"hard disk or on a usb key created with, e.g.:"
msgstr ""
@@ -634,28 +633,28 @@ msgstr "3~ Capas personalizadas"
#: en/user_customization-runtime.ssi:151
msgid ""
"A volume with the label #{custom-ov}# can be configured to make arbitrary "
-"directories persistent. The file #{live.persist}#, located on the volume's "
-"filesystem root, controls which directories it makes persistent, and in "
-"which way."
+"directories persistent. The file #{live-persistence.conf}#, located on the "
+"volume's filesystem root, controls which directories it makes persistent, "
+"and in which way."
msgstr ""
"Un volumen con la etiqueta #{custom-ov}# puede ser personalizado para crear "
-"arbitrariamente directorios persistentes. El fichero #{live.persist}#, "
-"situado en el sistema de ficheros raiz del volumen, controla que directorios "
-"hace persistentes y también de que manera."
+"arbitrariamente directorios persistentes. El fichero #{live-persistence.conf}"
+"#, situado en el sistema de ficheros raiz del volumen, controla que "
+"directorios hace persistentes y también de que manera."
#. type: Plain text
#: en/user_customization-runtime.ssi:153
msgid ""
"How custom overlay mounts are configured is described in full detail in the "
-"live.persist(5) man page, but a simple example should be sufficient for most "
-"uses. Let's say we want to make our home directory and APT cache persistent "
-"in an ext4 filesystem on the /dev/sdb1 partition:"
+"live-persistence.conf(5) man page, but a simple example should be sufficient "
+"for most uses. Let's say we want to make our home directory and APT cache "
+"persistent in an ext4 filesystem on the /dev/sdb1 partition:"
msgstr ""
-"En la página de manual de live.persist(5) se explica en detalle cómo se "
-"configura el montaje de las capas, pero un sencillo ejemplo es suficiente "
-"para la mayoría de los casos. Supongamos que queremos crear nuestro "
-"directorio home y APT cache persistentes en un sistema de ficheros ext4 en "
-"la partición /dev/sdb1:"
+"En la página de manual de live-persistence.conf(5) se explica en detalle "
+"cómo se configura el montaje de las capas, pero un sencillo ejemplo es "
+"suficiente para la mayoría de los casos. Supongamos que queremos crear "
+"nuestro directorio home y APT cache persistentes en un sistema de ficheros "
+"ext4 en la partición /dev/sdb1:"
#. type: Plain text
#: en/user_customization-runtime.ssi:160
@@ -663,53 +662,53 @@ msgstr ""
msgid ""
" $ mkfs.ext4 -L custom-ov /dev/sdb1\n"
" $ mount -t ext4 /dev/sdb1 /mnt\n"
-" $ echo \"/home\" >> /mnt/live.persist\n"
-" $ echo \"/var/cache/apt\" >> /mnt/live.persist\n"
+" $ echo \"/home\" >> /mnt/live-persistence.conf\n"
+" $ echo \"/var/cache/apt\" >> /mnt/live-persistence.conf\n"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:164
msgid ""
"Then we reboot. During the first boot the contents of #{/home}# and #{/var/"
-"cache/apt}# will be copied into the persistent volume, and from then on all "
-"changes to these directories will live in the persistent volume. Please note "
-"that any paths listed in the #{live.persist}# file cannot contain white "
-"spaces or the special #{.}# and #{..}# path components. Also, neither #{/"
-"live}# (or any of its sub-directories) nor #{/}# can be made persistent "
-"using custom mounts (for the latter, use the #{full-ov}# type persistence "
-"described above)."
+"cache/apt}# will be copied into the persistence volume, and from then on all "
+"changes to these directories will live in the persistence volume. Please "
+"note that any paths listed in the #{live-persistence.conf}# file cannot "
+"contain white spaces or the special #{.}# and #{..}# path components. Also, "
+"neither #{/live}# (or any of its sub-directories) nor #{/}# can be made "
+"persistent using custom mounts (for the latter, use the #{full-ov}# type "
+"persistence described above)."
msgstr ""
"Entonces reiniciamos. Durante el primer arranque los contenidos de #{/home}# "
"y #{/var/cache/apt}# se copiarán en el volumen persistente y a partir de ese "
"momento todos los cambios en esos directorios se guardarán allí. Tener en "
-"cuenta que los rutas listadas en el fichero #{live.persist}# no pueden "
-"contener espacios en blanco ni los componentes especiales #{.}# y #{..}#. "
-"Además ni #{/live}# (o ninguno de sus sub-directorios) ni #{/}# pueden "
-"hacerse persistentes montándolos de forma personalizada. Para este último, "
-"usar el tipo de persistencia #{full-ov}# descrito anteriormente."
+"cuenta que las rutas listadas en el fichero #{live-persistence.conf}# no "
+"pueden contener espacios en blanco ni los componentes especiales #{.}# y #"
+"{..}#. Además, ni #{/live}# (o ninguno de sus sub-directorios) ni #{/}# "
+"pueden hacerse persistentes montándolos de forma personalizada. Para esto "
+"último, usar el tipo de persistencia #{full-ov}# descrito anteriormente."
#. type: Plain text
#: en/user_customization-runtime.ssi:166
msgid ""
-"Several different custom overlay volumes (with their own #{live.persist}# "
-"files) can be used at the same time, but if several volumes make the same "
-"directory persistent, only one of them will be used. If any two mounts are "
-"\"nested\" (i.e. one is a sub-directory of the other) the parent will be "
+"Several different custom overlay volumes (with their own #{live-persistence."
+"conf}# files) can be used at the same time, but if several volumes make the "
+"same directory persistent, only one of them will be used. If any two mounts "
+"are \"nested\" (i.e. one is a sub-directory of the other) the parent will be "
"mounted before the child so no mount will be hidden by the other. Nested "
-"custom mounts are problematic if they are listed in the same #{live.persist}"
-"# file. See the live.persist(5) man page for how to handle that case if you "
-"really need it (hint: you usually don't)."
+"custom mounts are problematic if they are listed in the same #{live-"
+"persistence.conf}# file. See the live-persistence.conf(5) man page for how "
+"to handle that case if you really need it (hint: you usually don't)."
msgstr ""
"Se puede usar diferentes volúmenes de capas personalizados al mismo tiempo "
-"(con sus propios ficheros #{live.persist}#) pero si varios volúmenes hacen "
-"que un mismo directorio sea persistente, sólo uno de ellos será usado. Si "
-"dos unidades montadas están \"anidadas\" (es decir, una es un sub-directorio "
-"de la otra) el directorio superior será montado antes que el inferior de "
-"este modo no quedará uno escondido por el otro. La personalización de los "
-"montajes anidadados es problemática si están listados en el mismo fichero #"
-"{live.persist}#. Consultar la página de manual de live.persist(5) para ver "
-"como manejar ese caso si realmente es necesario. (aclaración: normalmente no "
-"lo es)."
+"(con sus propios ficheros #{live-persistence.conf}#) pero si varios "
+"volúmenes hacen que un mismo directorio sea persistente, sólo uno de ellos "
+"será usado. Si dos unidades montadas están \"anidadas\" (es decir, una es un "
+"sub-directorio de la otra) el directorio superior será montado antes que el "
+"inferior de este modo no quedará uno escondido por el otro. La "
+"personalización de los montajes anidadados es problemática si están listados "
+"en el mismo fichero #{live-persistence.conf}#. Consultar la página de manual "
+"de live-persistence.conf(5) para ver como manejar ese caso si realmente es "
+"necesario. (aclaración: normalmente no lo es)."
#. type: Plain text
#: en/user_customization-runtime.ssi:168
@@ -720,13 +719,13 @@ msgstr "3~ Instantáneas"
#: en/user_customization-runtime.ssi:170
msgid ""
"Snapshots are collections of files and directories which are not mounted "
-"while running but which are copied from a persistent volume to the system "
+"while running but which are copied from a persistence volume to the system "
"(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The "
"volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive "
"named #{live-sn.cpio.gz}#. A power interruption during run time could lead "
"to data loss, hence, if you have important changes, invoke #{live-snapshot --"
"refresh}# as often as needed. This type of persistence, since it does not "
-"write continuously to the persistent media, is the most flash-based device "
+"write continuously to the persistence media, is the most flash-based device "
"friendly and the fastest of all the persistence systems, but it occupies as "
"much RAM as the size of the uncompressed snapshot."
msgstr ""
@@ -760,27 +759,27 @@ msgstr "Las instantáneas no pueden manejar el borrado de ficheros."
#. type: Plain text
#: en/user_customization-runtime.ssi:176
-msgid "3~ Persistent SubText"
+msgid "3~ Persistence SubText"
msgstr "3~ SubText persistente"
#. type: Plain text
#: en/user_customization-runtime.ssi:178
msgid ""
-"If a user would need multiple persistent storage of the same type for "
+"If a user would need multiple persistence storage of the same type for "
"different locations or testing, such as #{full-ov-nonwork}# and #{full-ov-"
-"work}#, the boot parameter #{persistent-subtext}# used in conjunction with "
-"the boot parameter #{persistent}# will allow for multiple but unique "
-"persistent media. An example would be if a user wanted to use a persistent "
+"work}#, the boot parameter #{persistence-subtext}# used in conjunction with "
+"the boot parameter #{persistence}# will allow for multiple but unique "
+"persistence media. An example would be if a user wanted to use a persistence "
"partition labeled #{live-sn-subText}# they would use the boot parameters of: "
-"#{persistent}# #{persistent-subtext=subText}#."
+"#{persistence}# #{persistence-subtext=subText}#."
msgstr ""
"Si un usuario necesita un almacenamiento persistente múltiple del mismo tipo "
"para diferentes lugares o pruebas, tales como #{full-ov-nonwork}# y #{full-"
-"ov-work}#, el parámetro de arranque #{persistent-subtext}# usado junto con "
-"el parámetro de arranque #{persistent}# permitirá medios de almacenamiento "
+"ov-work}#, el parámetro de arranque #{persistence-subtext}# usado junto con "
+"el parámetro de arranque #{persistence}# permitirá medios de almacenamiento "
"persistentes múltiples pero únicos. Un ejemplo sería, si un usuario desea "
"utilizar una partición persistente etiquetada #{live-sn-subText}# usaría los "
-"parámetros de arranque: #{persistent}# #{persistent-subtext=subText}#."
+"parámetros de arranque: #{persistence}# #{persistence-subtext=subText}#."
#. type: Plain text
#: en/user_customization-runtime.ssi:180
diff --git a/manual/po/fr/user_customization-runtime.ssi.po b/manual/po/fr/user_customization-runtime.ssi.po
index d69b039..e87400d 100644
--- a/manual/po/fr/user_customization-runtime.ssi.po
+++ b/manual/po/fr/user_customization-runtime.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual\n"
-"POT-Creation-Date: 2012-04-08 12:15+0300\n"
+"POT-Creation-Date: 2012-06-03 20:02+0300\n"
"PO-Revision-Date: 2012-04-29 15:48+0200\n"
"Last-Translator: Carlos Zuferri «chals» <chals at altorricon.com>\n"
"Language-Team: <debian-live at lists.debian.org>\n"
@@ -17,11 +17,10 @@ msgstr ""
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. type: Plain text
-#: en/about_manual.ssi:90 en/about_manual.ssi:98 en/about_manual.ssi:106
-#: en/about_manual.ssi:114 en/about_manual.ssi:122 en/about_manual.ssi:130
-#: en/about_manual.ssi:142 en/about_manual.ssi:155 en/about_manual.ssi:168
-#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/about_manual.ssi:195
-#: en/about_manual.ssi:203 en/project_bugs.ssi:60
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:140 en/about_manual.ssi:153 en/about_manual.ssi:166
+#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:30 en/project_coding-style.ssi:40
#: en/project_coding-style.ssi:53 en/project_coding-style.ssi:63
#: en/project_coding-style.ssi:94 en/project_coding-style.ssi:102
@@ -88,11 +87,10 @@ msgid "code{"
msgstr "code{"
#. type: Plain text
-#: en/about_manual.ssi:94 en/about_manual.ssi:102 en/about_manual.ssi:110
-#: en/about_manual.ssi:118 en/about_manual.ssi:126 en/about_manual.ssi:134
-#: en/about_manual.ssi:151 en/about_manual.ssi:164 en/about_manual.ssi:173
-#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/about_manual.ssi:199
-#: en/about_manual.ssi:207 en/project_bugs.ssi:64
+#: en/about_manual.ssi:92 en/about_manual.ssi:100 en/about_manual.ssi:108
+#: en/about_manual.ssi:116 en/about_manual.ssi:124 en/about_manual.ssi:132
+#: en/about_manual.ssi:149 en/about_manual.ssi:162 en/about_manual.ssi:171
+#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:36 en/project_coding-style.ssi:47
#: en/project_coding-style.ssi:59 en/project_coding-style.ssi:70
#: en/project_coding-style.ssi:98 en/project_coding-style.ssi:106
@@ -442,15 +440,15 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:96
msgid ""
-"Persistence is a common name for different kinds of solutions for saving "
+"'Persistence' is a common name for different kinds of solutions for saving "
"across reboots some, or all, of this run-time evolution of the system. To "
"understand how it could work it could be handy to know that even if the "
"system is booted and run from read-only media, modification to the files and "
"directories are written on writable media, typically a ram disk (tmpfs) and "
"ram disks' data do not survive reboots."
msgstr ""
-"La persistance est un nom commun pour les différents types de solutions pour "
-"sauver, après un redémarrage, certaines ou toutes les données, de cette "
+"La «persistance» est un nom commun pour les différents types de solutions "
+"pour sauver, après un redémarrage, certaines ou toutes les données, de cette "
"évolution pendant l'exécution du système. Pour comprendre comment cela "
"pourrait fonctionner il pourrait être utile de savoir que même si le système "
"est démarré et exécuté à partir d'un support en lecture seule, la "
@@ -465,23 +463,24 @@ msgid ""
"medium like local storage media, a network share or even a session of a "
"multisession (re)writable CD/DVD. All these media are supported in Debian "
"Live in different ways, and all but the last one require a special boot "
-"parameter to be specified at boot time: #{persistent}#."
+"parameter to be specified at boot time: #{persistence}#."
msgstr ""
"Les données stockées sur ce disque virtuel doivent être enregistrées sur un "
"support inscriptible persistant comme supports de stockage locaux, un "
"partage réseau ou même une séance d'un CD/DVD multisession (ré)inscriptible. "
"Tous ces supports sont pris en charge dans Debian Live de différentes "
"manières, et tous, moins le dernier, nécessitent un paramètre d'amorçage "
-"spéciale à préciser au moment du démarrage: #{persistent}#."
+"spéciale à préciser au moment du démarrage: #{persistence}#."
#. type: Plain text
#: en/user_customization-runtime.ssi:100
msgid ""
-"If the boot parameter #{persistent}# is set (and #{nopersistent}# is not "
+"If the boot parameter #{persistence}# is set (and #{nopersistence}# is not "
"set), local storage media (e.g. hard disks, USB drives) will be probed for "
-"persistent volumes during boot. A persistent volume is any of the following:"
+"persistence volumes during boot. A persistence volume is any of the "
+"following:"
msgstr ""
-"Si le paramètre de démarrage #{persistent}# est réglé (et #{nopersistent}# "
+"Si le paramètre de démarrage #{persistence}# est réglé (et #{nopersistence}# "
"n'est pas utilisé), les supports de stockage locaux (par exemple les disques "
"durs, clés USB) seront examinés pour trouver des volumes persistants pendant "
"le démarrage. Un volume persistant est un des éléments suivants:"
@@ -515,7 +514,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:108
msgid ""
-"It is possible to restrict which types of persistent volumes to use by "
+"It is possible to restrict which types of persistence volumes to use by "
"specifying certain boot parameters described in the live-boot(7) man page. "
"The \"identifying labels\" referred to above can be any of the following:"
msgstr ""
@@ -526,7 +525,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:110
-msgid "_* #{full-ov}# for full persistent overlays."
+msgid "_* #{full-ov}# for full persistence overlays."
msgstr "_* #{full-ov}# pour couches de persistance pleine."
#. type: Plain text
@@ -546,7 +545,7 @@ msgstr "_* #{home-sn}# pour instantanés du /home."
#. type: Plain text
#: en/user_customization-runtime.ssi:118
-msgid "3~ Full persistent overlays"
+msgid "3~ Full persistence overlays"
msgstr "3~ Couches de persistance pleine"
#. type: Plain text
@@ -554,7 +553,7 @@ msgstr "3~ Couches de persistance pleine"
msgid ""
"By 'full persistence' it is meant that instead of using a tmpfs for storing "
"modifications to the read-only media (with the copy-on-write, COW, system) a "
-"persistent volume is used. For this type of persistence the volume label "
+"persistence volume is used. For this type of persistence the volume label "
"must be #{full-ov}#. This could, for instance, be an ext4 partition on a "
"hard disk or on a usb key created with, e.g.:"
msgstr ""
@@ -628,28 +627,28 @@ msgstr "3~ Couches personnalisées"
#: en/user_customization-runtime.ssi:151
msgid ""
"A volume with the label #{custom-ov}# can be configured to make arbitrary "
-"directories persistent. The file #{live.persist}#, located on the volume's "
-"filesystem root, controls which directories it makes persistent, and in "
-"which way."
+"directories persistent. The file #{live-persistence.conf}#, located on the "
+"volume's filesystem root, controls which directories it makes persistent, "
+"and in which way."
msgstr ""
"Un volume avec l'étiquette #{custom-ov}# peut être configuré pour créer des "
-"répertoires persistants arbitraires. Le fichier #{live.persist}#, situé sur "
-"le système de fichiers racine du volume, contrôle quels répertoires il fait "
-"persistants, et de quelle manière."
+"répertoires persistants arbitraires. Le fichier #{live-persistence.conf}#, "
+"situé sur le système de fichiers racine du volume, contrôle quels "
+"répertoires il fait persistants, et de quelle manière."
#. type: Plain text
#: en/user_customization-runtime.ssi:153
msgid ""
"How custom overlay mounts are configured is described in full detail in the "
-"live.persist(5) man page, but a simple example should be sufficient for most "
-"uses. Let's say we want to make our home directory and APT cache persistent "
-"in an ext4 filesystem on the /dev/sdb1 partition:"
+"live-persistence.conf(5) man page, but a simple example should be sufficient "
+"for most uses. Let's say we want to make our home directory and APT cache "
+"persistent in an ext4 filesystem on the /dev/sdb1 partition:"
msgstr ""
"Comment on configure monter des couches personnalisées est décrit en détail "
-"dans la page de manuel live.persist(5), mais un simple exemple devrait être "
-"suffisant pour la plupart des utilisations. Imaginons que nous voulons faire "
-"notre répertoire personnel et APT cache persistants dans un système de "
-"fichiers ext4 sur la partition /dev/sdb1:"
+"dans la page de manuel live-persistence.conf(5), mais un simple exemple "
+"devrait être suffisant pour la plupart des utilisations. Imaginons que nous "
+"voulons faire notre répertoire personnel et APT cache persistants dans un "
+"système de fichiers ext4 sur la partition /dev/sdb1:"
#. type: Plain text
#: en/user_customization-runtime.ssi:160
@@ -657,53 +656,54 @@ msgstr ""
msgid ""
" $ mkfs.ext4 -L custom-ov /dev/sdb1\n"
" $ mount -t ext4 /dev/sdb1 /mnt\n"
-" $ echo \"/home\" >> /mnt/live.persist\n"
-" $ echo \"/var/cache/apt\" >> /mnt/live.persist\n"
+" $ echo \"/home\" >> /mnt/live-persistence.conf\n"
+" $ echo \"/var/cache/apt\" >> /mnt/live-persistence.conf\n"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:164
msgid ""
"Then we reboot. During the first boot the contents of #{/home}# and #{/var/"
-"cache/apt}# will be copied into the persistent volume, and from then on all "
-"changes to these directories will live in the persistent volume. Please note "
-"that any paths listed in the #{live.persist}# file cannot contain white "
-"spaces or the special #{.}# and #{..}# path components. Also, neither #{/"
-"live}# (or any of its sub-directories) nor #{/}# can be made persistent "
-"using custom mounts (for the latter, use the #{full-ov}# type persistence "
-"described above)."
+"cache/apt}# will be copied into the persistence volume, and from then on all "
+"changes to these directories will live in the persistence volume. Please "
+"note that any paths listed in the #{live-persistence.conf}# file cannot "
+"contain white spaces or the special #{.}# and #{..}# path components. Also, "
+"neither #{/live}# (or any of its sub-directories) nor #{/}# can be made "
+"persistent using custom mounts (for the latter, use the #{full-ov}# type "
+"persistence described above)."
msgstr ""
"Alors nous redémarrons. Lors du premier démarrage les contenus du #{/home}# "
"et #{/var/cache/apt}# seront copiés dans le volume persistant, et à partir "
"de ce moment tous les changements dans ces répertoires seront stockés dans "
"le volume persistant. S'il vous plaît souligner que les chemins d'accès aux "
-"répertoriés dans le fichier #{live.persist}# ne peuvent pas contenir "
-"d'espaces blancs ou les éléments spéciaux #{.}# et #{..}#. En outre, ni #{/"
-"live}# (ou un de ses sous-répertoires), ni #{/}# peuvent être rendus "
-"persistants en utilisant custom mounts (pour ce dernier, utilisez la "
+"répertoriés dans le fichier #{live-persistence.conf}# ne peuvent pas "
+"contenir d'espaces blancs ou les éléments spéciaux #{.}# et #{..}#. En "
+"outre, ni #{/live}# (ou un de ses sous-répertoires), ni #{/}# peuvent être "
+"rendus persistants en utilisant custom mounts (pour ce dernier, utilisez la "
"persistance #{full-ov}# décrite ci-dessus)."
#. type: Plain text
#: en/user_customization-runtime.ssi:166
msgid ""
-"Several different custom overlay volumes (with their own #{live.persist}# "
-"files) can be used at the same time, but if several volumes make the same "
-"directory persistent, only one of them will be used. If any two mounts are "
-"\"nested\" (i.e. one is a sub-directory of the other) the parent will be "
+"Several different custom overlay volumes (with their own #{live-persistence."
+"conf}# files) can be used at the same time, but if several volumes make the "
+"same directory persistent, only one of them will be used. If any two mounts "
+"are \"nested\" (i.e. one is a sub-directory of the other) the parent will be "
"mounted before the child so no mount will be hidden by the other. Nested "
-"custom mounts are problematic if they are listed in the same #{live.persist}"
-"# file. See the live.persist(5) man page for how to handle that case if you "
-"really need it (hint: you usually don't)."
+"custom mounts are problematic if they are listed in the same #{live-"
+"persistence.conf}# file. See the live-persistence.conf(5) man page for how "
+"to handle that case if you really need it (hint: you usually don't)."
msgstr ""
"Plusieurs volumes de couches personnalisées différents (avec leurs propres "
-"fichiers #{live.persist}#) peuvent être utilisées au même temps, mais si "
-"plusieurs volumes font le même répertoire persistant, un seul d'entre eux "
-"sera utilisé. Si les deux sont «imbriqués» (un est un sous-répertoire de "
-"l'autre) le premier sera monté avant que le secondaire de sorte que aucun "
-"sera caché par l'autre. Monter des éléments personnalisés imbriqués est "
-"problématique s'ils sont énumérés dans le même fichier #{live.persist}#. "
-"Voir la page de manuel live.persist(5) pour savoir comment gérer ce cas, si "
-"vous avez vraiment besoin (remarque: vous n'avez généralement pas)."
+"fichiers #{live-persistence.conf}#) peuvent être utilisées au même temps, "
+"mais si plusieurs volumes font le même répertoire persistant, un seul "
+"d'entre eux sera utilisé. Si les deux sont «imbriqués» (un est un sous-"
+"répertoire de l'autre) le premier sera monté avant que le secondaire de "
+"sorte que aucun sera caché par l'autre. Monter des éléments personnalisés "
+"imbriqués est problématique s'ils sont énumérés dans le même fichier #{live-"
+"persistence.conf}#. Voir la page de manuel live-persistence.conf(5) pour "
+"savoir comment gérer ce cas, si vous avez vraiment besoin (remarque: vous "
+"n'avez généralement pas)."
#. type: Plain text
#: en/user_customization-runtime.ssi:168
@@ -714,13 +714,13 @@ msgstr "3~ Instantanés"
#: en/user_customization-runtime.ssi:170
msgid ""
"Snapshots are collections of files and directories which are not mounted "
-"while running but which are copied from a persistent volume to the system "
+"while running but which are copied from a persistence volume to the system "
"(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The "
"volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive "
"named #{live-sn.cpio.gz}#. A power interruption during run time could lead "
"to data loss, hence, if you have important changes, invoke #{live-snapshot --"
"refresh}# as often as needed. This type of persistence, since it does not "
-"write continuously to the persistent media, is the most flash-based device "
+"write continuously to the persistence media, is the most flash-based device "
"friendly and the fastest of all the persistence systems, but it occupies as "
"much RAM as the size of the uncompressed snapshot."
msgstr ""
@@ -755,28 +755,28 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:176
-msgid "3~ Persistent SubText"
+msgid "3~ Persistence SubText"
msgstr "3~ SubText persistant"
#. type: Plain text
#: en/user_customization-runtime.ssi:178
msgid ""
-"If a user would need multiple persistent storage of the same type for "
+"If a user would need multiple persistence storage of the same type for "
"different locations or testing, such as #{full-ov-nonwork}# and #{full-ov-"
-"work}#, the boot parameter #{persistent-subtext}# used in conjunction with "
-"the boot parameter #{persistent}# will allow for multiple but unique "
-"persistent media. An example would be if a user wanted to use a persistent "
+"work}#, the boot parameter #{persistence-subtext}# used in conjunction with "
+"the boot parameter #{persistence}# will allow for multiple but unique "
+"persistence media. An example would be if a user wanted to use a persistence "
"partition labeled #{live-sn-subText}# they would use the boot parameters of: "
-"#{persistent}# #{persistent-subtext=subText}#."
+"#{persistence}# #{persistence-subtext=subText}#."
msgstr ""
"Si un utilisateur a besoin de stockages persistants multiples du même type "
"pour différents endroits ou l'essai, tel que #{full-ov-nonwork}# et #{full-"
-"ov-work}#, le paramètre de démarrage #{persistent-subtext}# utilisé en "
-"conjonction avec le paramètre de démarrage #{persistent}# permettra "
+"ov-work}#, le paramètre de démarrage #{persistence-subtext}# utilisé en "
+"conjonction avec le paramètre de démarrage #{persistence}# permettra "
"multiples, mais uniques, supports persistants. Un exemple serait le cas si "
"un utilisateur voudrait utiliser une partition persistante étiquetée #{live-"
-"sn-subText}# il utiliserait les paramètres de démarrage: #{persistent}# #"
-"{persistent-subtext=subText}#."
+"sn-subText}# il utiliserait les paramètres de démarrage: #{persistence}# #"
+"{persistence-subtext=subText}#."
#. type: Plain text
#: en/user_customization-runtime.ssi:180
diff --git a/manual/po/it/user_customization-runtime.ssi.po b/manual/po/it/user_customization-runtime.ssi.po
index bbecf32..425e904 100644
--- a/manual/po/it/user_customization-runtime.ssi.po
+++ b/manual/po/it/user_customization-runtime.ssi.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual\n"
-"POT-Creation-Date: 2012-04-08 12:15+0300\n"
+"POT-Creation-Date: 2012-06-03 20:02+0300\n"
"PO-Revision-Date: 2012-04-02 23:25+0100\n"
"Last-Translator: skizzhg <skizzhg at gmx.com>\n"
"Language-Team: Italian <tp at lists.linux.it>\n"
@@ -17,11 +17,10 @@ msgstr ""
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. type: Plain text
-#: en/about_manual.ssi:90 en/about_manual.ssi:98 en/about_manual.ssi:106
-#: en/about_manual.ssi:114 en/about_manual.ssi:122 en/about_manual.ssi:130
-#: en/about_manual.ssi:142 en/about_manual.ssi:155 en/about_manual.ssi:168
-#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/about_manual.ssi:195
-#: en/about_manual.ssi:203 en/project_bugs.ssi:60
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:140 en/about_manual.ssi:153 en/about_manual.ssi:166
+#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:30 en/project_coding-style.ssi:40
#: en/project_coding-style.ssi:53 en/project_coding-style.ssi:63
#: en/project_coding-style.ssi:94 en/project_coding-style.ssi:102
@@ -88,11 +87,10 @@ msgid "code{"
msgstr "code{"
#. type: Plain text
-#: en/about_manual.ssi:94 en/about_manual.ssi:102 en/about_manual.ssi:110
-#: en/about_manual.ssi:118 en/about_manual.ssi:126 en/about_manual.ssi:134
-#: en/about_manual.ssi:151 en/about_manual.ssi:164 en/about_manual.ssi:173
-#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/about_manual.ssi:199
-#: en/about_manual.ssi:207 en/project_bugs.ssi:64
+#: en/about_manual.ssi:92 en/about_manual.ssi:100 en/about_manual.ssi:108
+#: en/about_manual.ssi:116 en/about_manual.ssi:124 en/about_manual.ssi:132
+#: en/about_manual.ssi:149 en/about_manual.ssi:162 en/about_manual.ssi:171
+#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:36 en/project_coding-style.ssi:47
#: en/project_coding-style.ssi:59 en/project_coding-style.ssi:70
#: en/project_coding-style.ssi:98 en/project_coding-style.ssi:106
@@ -434,7 +432,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:96
msgid ""
-"Persistence is a common name for different kinds of solutions for saving "
+"'Persistence' is a common name for different kinds of solutions for saving "
"across reboots some, or all, of this run-time evolution of the system. To "
"understand how it could work it could be handy to know that even if the "
"system is booted and run from read-only media, modification to the files and "
@@ -455,24 +453,25 @@ msgid ""
"medium like local storage media, a network share or even a session of a "
"multisession (re)writable CD/DVD. All these media are supported in Debian "
"Live in different ways, and all but the last one require a special boot "
-"parameter to be specified at boot time: #{persistent}#."
+"parameter to be specified at boot time: #{persistence}#."
msgstr ""
"I dati immagazzinati su questo ramdisk andrebbero salvati un supporto "
"scrivibile persistente come un supporto di memorizzazione locale, una "
"condivisione di rete o anche una sessione di un CD/DVD riscrivibile "
"multisessione. Tutti questi supporti sono gestiti in Debian Live in modi "
"differenti, e tutti tranne l'ultimo richiedono un parametro d'avvio speciale "
-"da specificare all'avvio: #{persistent}#."
+"da specificare all'avvio: #{persistence}#."
#. type: Plain text
#: en/user_customization-runtime.ssi:100
msgid ""
-"If the boot parameter #{persistent}# is set (and #{nopersistent}# is not "
+"If the boot parameter #{persistence}# is set (and #{nopersistence}# is not "
"set), local storage media (e.g. hard disks, USB drives) will be probed for "
-"persistent volumes during boot. A persistent volume is any of the following:"
+"persistence volumes during boot. A persistence volume is any of the "
+"following:"
msgstr ""
-"Se il parametro di boot #{persistent}# è impostato (e non lo è #"
-"{nopersistent}#), i supporti di memorizzazione locali (hard disk, "
+"Se il parametro di boot #{persistence}# è impostato (e non lo è #"
+"{nopersistence}#), i supporti di memorizzazione locali (hard disk, "
"dispositivi USB) saranno rilevati come volumi persistenti durante l'avvio. "
"Un volume persistente è uno dei seguenti:"
@@ -504,7 +503,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:108
msgid ""
-"It is possible to restrict which types of persistent volumes to use by "
+"It is possible to restrict which types of persistence volumes to use by "
"specifying certain boot parameters described in the live-boot(7) man page. "
"The \"identifying labels\" referred to above can be any of the following:"
msgstr ""
@@ -514,7 +513,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:110
-msgid "_* #{full-ov}# for full persistent overlays."
+msgid "_* #{full-ov}# for full persistence overlays."
msgstr "_* #{full-ov}# per strati di persistenza completa."
#. type: Plain text
@@ -534,7 +533,7 @@ msgstr "_* #{home-sn}# per istantanee della /home."
#. type: Plain text
#: en/user_customization-runtime.ssi:118
-msgid "3~ Full persistent overlays"
+msgid "3~ Full persistence overlays"
msgstr "3~ Strati di persistenza completa"
#. type: Plain text
@@ -542,7 +541,7 @@ msgstr "3~ Strati di persistenza completa"
msgid ""
"By 'full persistence' it is meant that instead of using a tmpfs for storing "
"modifications to the read-only media (with the copy-on-write, COW, system) a "
-"persistent volume is used. For this type of persistence the volume label "
+"persistence volume is used. For this type of persistence the volume label "
"must be #{full-ov}#. This could, for instance, be an ext4 partition on a "
"hard disk or on a usb key created with, e.g.:"
msgstr ""
@@ -618,25 +617,25 @@ msgstr "3~ Strati personalizzati"
#: en/user_customization-runtime.ssi:151
msgid ""
"A volume with the label #{custom-ov}# can be configured to make arbitrary "
-"directories persistent. The file #{live.persist}#, located on the volume's "
-"filesystem root, controls which directories it makes persistent, and in "
-"which way."
+"directories persistent. The file #{live-persistence.conf}#, located on the "
+"volume's filesystem root, controls which directories it makes persistent, "
+"and in which way."
msgstr ""
"Un volume con una label #{custom-ov}# può essere configurato per creare "
-"directory persistenti arbitrarie. Il file #{live.persist}#, situato nella "
-"directory radice del filesystem del volume, controlla quali rendere "
+"directory persistenti arbitrarie. Il file #{live-persistence.conf}#, situato "
+"nella directory radice del filesystem del volume, controlla quali rendere "
"persistenti e in che modo."
#. type: Plain text
#: en/user_customization-runtime.ssi:153
msgid ""
"How custom overlay mounts are configured is described in full detail in the "
-"live.persist(5) man page, but a simple example should be sufficient for most "
-"uses. Let's say we want to make our home directory and APT cache persistent "
-"in an ext4 filesystem on the /dev/sdb1 partition:"
+"live-persistence.conf(5) man page, but a simple example should be sufficient "
+"for most uses. Let's say we want to make our home directory and APT cache "
+"persistent in an ext4 filesystem on the /dev/sdb1 partition:"
msgstr ""
-"Nella manpage di live.persist(5) è descritto dettagliatamente come è "
-"configurato il mount degli strati personalizzati, ma un semplice esempio "
+"Nella manpage di live-persistence.conf(5) è descritto dettagliatamente come "
+"è configurato il mount degli strati personalizzati, ma un semplice esempio "
"dovrebbe essere sufficiente per la maggior parte degli usi. Supponendo di "
"voler creare la directory home e quella della cache di APT in modo "
"persistente in un filesystem ext4 sulla partizione /dev/sdb1:"
@@ -647,52 +646,52 @@ msgstr ""
msgid ""
" $ mkfs.ext4 -L custom-ov /dev/sdb1\n"
" $ mount -t ext4 /dev/sdb1 /mnt\n"
-" $ echo \"/home\" >> /mnt/live.persist\n"
-" $ echo \"/var/cache/apt\" >> /mnt/live.persist\n"
+" $ echo \"/home\" >> /mnt/live-persistence.conf\n"
+" $ echo \"/var/cache/apt\" >> /mnt/live-persistence.conf\n"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:164
msgid ""
"Then we reboot. During the first boot the contents of #{/home}# and #{/var/"
-"cache/apt}# will be copied into the persistent volume, and from then on all "
-"changes to these directories will live in the persistent volume. Please note "
-"that any paths listed in the #{live.persist}# file cannot contain white "
-"spaces or the special #{.}# and #{..}# path components. Also, neither #{/"
-"live}# (or any of its sub-directories) nor #{/}# can be made persistent "
-"using custom mounts (for the latter, use the #{full-ov}# type persistence "
-"described above)."
+"cache/apt}# will be copied into the persistence volume, and from then on all "
+"changes to these directories will live in the persistence volume. Please "
+"note that any paths listed in the #{live-persistence.conf}# file cannot "
+"contain white spaces or the special #{.}# and #{..}# path components. Also, "
+"neither #{/live}# (or any of its sub-directories) nor #{/}# can be made "
+"persistent using custom mounts (for the latter, use the #{full-ov}# type "
+"persistence described above)."
msgstr ""
"Quindi riavviare. Durante il primo avvio il contenuto di #{/home}# e #{/var/"
"cache/apt}# saranno copiati nel volume persistente e da allora tutte le "
"modifiche a queste directory risiederanno in modo persistente sul volume. "
-"C'è da considerare che tutti i path elencati nel file #{live.persist}# non "
-"possono contenere spazi o i caratteri speciali #{.}# e #{..}#; inoltre, né #"
-"{/live}# (o nessuna delle sue sottodirectory) né #{/}# può essere resa "
-"persistente tramite i mount personalizzati (per l'ultimo usare la tipologia #"
-"{full-ov}# descritta prima)."
+"C'è da considerare che tutti i path elencati nel file #{live-persistence."
+"conf}# non possono contenere spazi o i caratteri speciali #{.}# e #{..}#; "
+"inoltre, né #{/live}# (o nessuna delle sue sottodirectory) né #{/}# può "
+"essere resa persistente tramite i mount personalizzati (per l'ultimo usare "
+"la tipologia #{full-ov}# descritta prima)."
#. type: Plain text
#: en/user_customization-runtime.ssi:166
msgid ""
-"Several different custom overlay volumes (with their own #{live.persist}# "
-"files) can be used at the same time, but if several volumes make the same "
-"directory persistent, only one of them will be used. If any two mounts are "
-"\"nested\" (i.e. one is a sub-directory of the other) the parent will be "
+"Several different custom overlay volumes (with their own #{live-persistence."
+"conf}# files) can be used at the same time, but if several volumes make the "
+"same directory persistent, only one of them will be used. If any two mounts "
+"are \"nested\" (i.e. one is a sub-directory of the other) the parent will be "
"mounted before the child so no mount will be hidden by the other. Nested "
-"custom mounts are problematic if they are listed in the same #{live.persist}"
-"# file. See the live.persist(5) man page for how to handle that case if you "
-"really need it (hint: you usually don't)."
+"custom mounts are problematic if they are listed in the same #{live-"
+"persistence.conf}# file. See the live-persistence.conf(5) man page for how "
+"to handle that case if you really need it (hint: you usually don't)."
msgstr ""
"Possono essere utilizzati svariati volumi di stratificazione personalizzati "
-"(con i rispettivi file #{live.persist}#) allo stesso tempo ma se questi "
-"creano la stessa directory persistente, ne verrà usata solo una. Se due "
-"directory montate sono \"nidificate\" (una è la sottodirectory dell'altra), "
-"la superiore sarà montata per prima, per cui nessuna operazione di mount "
-"verrà sovrastata dall'altra. I mount nidificati personalizzati sono "
-"problematici se sono elencati nello stesso file #{live.persist}. Se si ha "
-"davvero la necessità (in genere non si dovrebbe averla), consultare la "
-"manpage di live.persist(5) per sapere come gestire questo caso."
+"(con i rispettivi file #{live-persistence.conf}#) allo stesso tempo ma se "
+"questi creano la stessa directory persistente, ne verrà usata solo una. Se "
+"due directory montate sono \"nidificate\" (una è la sottodirectory "
+"dell'altra), la superiore sarà montata per prima, per cui nessuna operazione "
+"di mount verrà sovrastata dall'altra. I mount nidificati personalizzati sono "
+"problematici se sono elencati nello stesso file #{live-persistence.conf}. Se "
+"si ha davvero la necessità (in genere non si dovrebbe averla), consultare la "
+"manpage di live-persistence.conf(5) per sapere come gestire questo caso."
#. type: Plain text
#: en/user_customization-runtime.ssi:168
@@ -703,13 +702,13 @@ msgstr "3~ Istantanee"
#: en/user_customization-runtime.ssi:170
msgid ""
"Snapshots are collections of files and directories which are not mounted "
-"while running but which are copied from a persistent volume to the system "
+"while running but which are copied from a persistence volume to the system "
"(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The "
"volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive "
"named #{live-sn.cpio.gz}#. A power interruption during run time could lead "
"to data loss, hence, if you have important changes, invoke #{live-snapshot --"
"refresh}# as often as needed. This type of persistence, since it does not "
-"write continuously to the persistent media, is the most flash-based device "
+"write continuously to the persistence media, is the most flash-based device "
"friendly and the fastest of all the persistence systems, but it occupies as "
"much RAM as the size of the uncompressed snapshot."
msgstr ""
@@ -742,26 +741,26 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:176
-msgid "3~ Persistent SubText"
+msgid "3~ Persistence SubText"
msgstr "3~ Sottotesto persistente"
#. type: Plain text
#: en/user_customization-runtime.ssi:178
msgid ""
-"If a user would need multiple persistent storage of the same type for "
+"If a user would need multiple persistence storage of the same type for "
"different locations or testing, such as #{full-ov-nonwork}# and #{full-ov-"
-"work}#, the boot parameter #{persistent-subtext}# used in conjunction with "
-"the boot parameter #{persistent}# will allow for multiple but unique "
-"persistent media. An example would be if a user wanted to use a persistent "
+"work}#, the boot parameter #{persistence-subtext}# used in conjunction with "
+"the boot parameter #{persistence}# will allow for multiple but unique "
+"persistence media. An example would be if a user wanted to use a persistence "
"partition labeled #{live-sn-subText}# they would use the boot parameters of: "
-"#{persistent}# #{persistent-subtext=subText}#."
+"#{persistence}# #{persistence-subtext=subText}#."
msgstr ""
"Se un utente avesse bisogno di archiviazioni multiple dello stesso tipo per "
"differenti posti o per test, come #{full-ov-casa}# e #{full-ov-lavoro}#, il "
-"parametro d'avvio #{persistent-subtext}# usato in congiunzione con #"
+"parametro d'avvio #{persistence-subtext}# usato in congiunzione con #"
"{persistent}# permetterà supporti persistenti multipli ma univoci. Un "
"esempio potrebbe essere un utente che vuole usare una partizione etichettata "
-"come #{live-sn-sottotesto}#, userebbe: #{persistent}# #{persistent-"
+"come #{live-sn-sottotesto}#, userebbe: #{persistence}# #{persistence-"
"subtext=sottotesto}#."
#. type: Plain text
diff --git a/manual/po/pt_BR/user_customization-runtime.ssi.po b/manual/po/pt_BR/user_customization-runtime.ssi.po
index 37e595c..105b3bb 100644
--- a/manual/po/pt_BR/user_customization-runtime.ssi.po
+++ b/manual/po/pt_BR/user_customization-runtime.ssi.po
@@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual\n"
-"POT-Creation-Date: 2012-04-08 12:15+0300\n"
+"POT-Creation-Date: 2012-06-03 20:02+0300\n"
"PO-Revision-Date: 2010-11-30 11:40+0100\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -16,11 +16,10 @@ msgstr ""
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#. type: Plain text
-#: en/about_manual.ssi:90 en/about_manual.ssi:98 en/about_manual.ssi:106
-#: en/about_manual.ssi:114 en/about_manual.ssi:122 en/about_manual.ssi:130
-#: en/about_manual.ssi:142 en/about_manual.ssi:155 en/about_manual.ssi:168
-#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/about_manual.ssi:195
-#: en/about_manual.ssi:203 en/project_bugs.ssi:60
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:140 en/about_manual.ssi:153 en/about_manual.ssi:166
+#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:30 en/project_coding-style.ssi:40
#: en/project_coding-style.ssi:53 en/project_coding-style.ssi:63
#: en/project_coding-style.ssi:94 en/project_coding-style.ssi:102
@@ -87,11 +86,10 @@ msgid "code{"
msgstr "code{"
#. type: Plain text
-#: en/about_manual.ssi:94 en/about_manual.ssi:102 en/about_manual.ssi:110
-#: en/about_manual.ssi:118 en/about_manual.ssi:126 en/about_manual.ssi:134
-#: en/about_manual.ssi:151 en/about_manual.ssi:164 en/about_manual.ssi:173
-#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/about_manual.ssi:199
-#: en/about_manual.ssi:207 en/project_bugs.ssi:64
+#: en/about_manual.ssi:92 en/about_manual.ssi:100 en/about_manual.ssi:108
+#: en/about_manual.ssi:116 en/about_manual.ssi:124 en/about_manual.ssi:132
+#: en/about_manual.ssi:149 en/about_manual.ssi:162 en/about_manual.ssi:171
+#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:36 en/project_coding-style.ssi:47
#: en/project_coding-style.ssi:59 en/project_coding-style.ssi:70
#: en/project_coding-style.ssi:98 en/project_coding-style.ssi:106
@@ -377,7 +375,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:96
msgid ""
-"Persistence is a common name for different kinds of solutions for saving "
+"'Persistence' is a common name for different kinds of solutions for saving "
"across reboots some, or all, of this run-time evolution of the system. To "
"understand how it could work it could be handy to know that even if the "
"system is booted and run from read-only media, modification to the files and "
@@ -392,15 +390,16 @@ msgid ""
"medium like local storage media, a network share or even a session of a "
"multisession (re)writable CD/DVD. All these media are supported in Debian "
"Live in different ways, and all but the last one require a special boot "
-"parameter to be specified at boot time: #{persistent}#."
+"parameter to be specified at boot time: #{persistence}#."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:100
msgid ""
-"If the boot parameter #{persistent}# is set (and #{nopersistent}# is not "
+"If the boot parameter #{persistence}# is set (and #{nopersistence}# is not "
"set), local storage media (e.g. hard disks, USB drives) will be probed for "
-"persistent volumes during boot. A persistent volume is any of the following:"
+"persistence volumes during boot. A persistence volume is any of the "
+"following:"
msgstr ""
#. type: Plain text
@@ -425,14 +424,14 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:108
msgid ""
-"It is possible to restrict which types of persistent volumes to use by "
+"It is possible to restrict which types of persistence volumes to use by "
"specifying certain boot parameters described in the live-boot(7) man page. "
"The \"identifying labels\" referred to above can be any of the following:"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:110
-msgid "_* #{full-ov}# for full persistent overlays."
+msgid "_* #{full-ov}# for full persistence overlays."
msgstr ""
#. type: Plain text
@@ -452,7 +451,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:118
-msgid "3~ Full persistent overlays"
+msgid "3~ Full persistence overlays"
msgstr ""
#. type: Plain text
@@ -460,7 +459,7 @@ msgstr ""
msgid ""
"By 'full persistence' it is meant that instead of using a tmpfs for storing "
"modifications to the read-only media (with the copy-on-write, COW, system) a "
-"persistent volume is used. For this type of persistence the volume label "
+"persistence volume is used. For this type of persistence the volume label "
"must be #{full-ov}#. This could, for instance, be an ext4 partition on a "
"hard disk or on a usb key created with, e.g.:"
msgstr ""
@@ -520,18 +519,18 @@ msgstr ""
#: en/user_customization-runtime.ssi:151
msgid ""
"A volume with the label #{custom-ov}# can be configured to make arbitrary "
-"directories persistent. The file #{live.persist}#, located on the volume's "
-"filesystem root, controls which directories it makes persistent, and in "
-"which way."
+"directories persistent. The file #{live-persistence.conf}#, located on the "
+"volume's filesystem root, controls which directories it makes persistent, "
+"and in which way."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:153
msgid ""
"How custom overlay mounts are configured is described in full detail in the "
-"live.persist(5) man page, but a simple example should be sufficient for most "
-"uses. Let's say we want to make our home directory and APT cache persistent "
-"in an ext4 filesystem on the /dev/sdb1 partition:"
+"live-persistence.conf(5) man page, but a simple example should be sufficient "
+"for most uses. Let's say we want to make our home directory and APT cache "
+"persistent in an ext4 filesystem on the /dev/sdb1 partition:"
msgstr ""
#. type: Plain text
@@ -540,34 +539,34 @@ msgstr ""
msgid ""
" $ mkfs.ext4 -L custom-ov /dev/sdb1\n"
" $ mount -t ext4 /dev/sdb1 /mnt\n"
-" $ echo \"/home\" >> /mnt/live.persist\n"
-" $ echo \"/var/cache/apt\" >> /mnt/live.persist\n"
+" $ echo \"/home\" >> /mnt/live-persistence.conf\n"
+" $ echo \"/var/cache/apt\" >> /mnt/live-persistence.conf\n"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:164
msgid ""
"Then we reboot. During the first boot the contents of #{/home}# and #{/var/"
-"cache/apt}# will be copied into the persistent volume, and from then on all "
-"changes to these directories will live in the persistent volume. Please note "
-"that any paths listed in the #{live.persist}# file cannot contain white "
-"spaces or the special #{.}# and #{..}# path components. Also, neither #{/"
-"live}# (or any of its sub-directories) nor #{/}# can be made persistent "
-"using custom mounts (for the latter, use the #{full-ov}# type persistence "
-"described above)."
+"cache/apt}# will be copied into the persistence volume, and from then on all "
+"changes to these directories will live in the persistence volume. Please "
+"note that any paths listed in the #{live-persistence.conf}# file cannot "
+"contain white spaces or the special #{.}# and #{..}# path components. Also, "
+"neither #{/live}# (or any of its sub-directories) nor #{/}# can be made "
+"persistent using custom mounts (for the latter, use the #{full-ov}# type "
+"persistence described above)."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:166
msgid ""
-"Several different custom overlay volumes (with their own #{live.persist}# "
-"files) can be used at the same time, but if several volumes make the same "
-"directory persistent, only one of them will be used. If any two mounts are "
-"\"nested\" (i.e. one is a sub-directory of the other) the parent will be "
+"Several different custom overlay volumes (with their own #{live-persistence."
+"conf}# files) can be used at the same time, but if several volumes make the "
+"same directory persistent, only one of them will be used. If any two mounts "
+"are \"nested\" (i.e. one is a sub-directory of the other) the parent will be "
"mounted before the child so no mount will be hidden by the other. Nested "
-"custom mounts are problematic if they are listed in the same #{live.persist}"
-"# file. See the live.persist(5) man page for how to handle that case if you "
-"really need it (hint: you usually don't)."
+"custom mounts are problematic if they are listed in the same #{live-"
+"persistence.conf}# file. See the live-persistence.conf(5) man page for how "
+"to handle that case if you really need it (hint: you usually don't)."
msgstr ""
#. type: Plain text
@@ -579,13 +578,13 @@ msgstr ""
#: en/user_customization-runtime.ssi:170
msgid ""
"Snapshots are collections of files and directories which are not mounted "
-"while running but which are copied from a persistent volume to the system "
+"while running but which are copied from a persistence volume to the system "
"(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The "
"volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive "
"named #{live-sn.cpio.gz}#. A power interruption during run time could lead "
"to data loss, hence, if you have important changes, invoke #{live-snapshot --"
"refresh}# as often as needed. This type of persistence, since it does not "
-"write continuously to the persistent media, is the most flash-based device "
+"write continuously to the persistence media, is the most flash-based device "
"friendly and the fastest of all the persistence systems, but it occupies as "
"much RAM as the size of the uncompressed snapshot."
msgstr ""
@@ -604,19 +603,19 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:176
-msgid "3~ Persistent SubText"
+msgid "3~ Persistence SubText"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:178
msgid ""
-"If a user would need multiple persistent storage of the same type for "
+"If a user would need multiple persistence storage of the same type for "
"different locations or testing, such as #{full-ov-nonwork}# and #{full-ov-"
-"work}#, the boot parameter #{persistent-subtext}# used in conjunction with "
-"the boot parameter #{persistent}# will allow for multiple but unique "
-"persistent media. An example would be if a user wanted to use a persistent "
+"work}#, the boot parameter #{persistence-subtext}# used in conjunction with "
+"the boot parameter #{persistence}# will allow for multiple but unique "
+"persistence media. An example would be if a user wanted to use a persistence "
"partition labeled #{live-sn-subText}# they would use the boot parameters of: "
-"#{persistent}# #{persistent-subtext=subText}#."
+"#{persistence}# #{persistence-subtext=subText}#."
msgstr ""
#. type: Plain text
diff --git a/manual/po/ro/user_customization-runtime.ssi.po b/manual/po/ro/user_customization-runtime.ssi.po
index c0d962d..b18fcac 100644
--- a/manual/po/ro/user_customization-runtime.ssi.po
+++ b/manual/po/ro/user_customization-runtime.ssi.po
@@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual\n"
-"POT-Creation-Date: 2012-04-08 12:15+0300\n"
+"POT-Creation-Date: 2012-06-03 20:02+0300\n"
"PO-Revision-Date: 2010-11-30 11:40+0100\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -17,11 +17,10 @@ msgstr ""
"20)) ? 1 : 2;\n"
#. type: Plain text
-#: en/about_manual.ssi:90 en/about_manual.ssi:98 en/about_manual.ssi:106
-#: en/about_manual.ssi:114 en/about_manual.ssi:122 en/about_manual.ssi:130
-#: en/about_manual.ssi:142 en/about_manual.ssi:155 en/about_manual.ssi:168
-#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/about_manual.ssi:195
-#: en/about_manual.ssi:203 en/project_bugs.ssi:60
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:140 en/about_manual.ssi:153 en/about_manual.ssi:166
+#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:30 en/project_coding-style.ssi:40
#: en/project_coding-style.ssi:53 en/project_coding-style.ssi:63
#: en/project_coding-style.ssi:94 en/project_coding-style.ssi:102
@@ -88,11 +87,10 @@ msgid "code{"
msgstr "code{"
#. type: Plain text
-#: en/about_manual.ssi:94 en/about_manual.ssi:102 en/about_manual.ssi:110
-#: en/about_manual.ssi:118 en/about_manual.ssi:126 en/about_manual.ssi:134
-#: en/about_manual.ssi:151 en/about_manual.ssi:164 en/about_manual.ssi:173
-#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/about_manual.ssi:199
-#: en/about_manual.ssi:207 en/project_bugs.ssi:64
+#: en/about_manual.ssi:92 en/about_manual.ssi:100 en/about_manual.ssi:108
+#: en/about_manual.ssi:116 en/about_manual.ssi:124 en/about_manual.ssi:132
+#: en/about_manual.ssi:149 en/about_manual.ssi:162 en/about_manual.ssi:171
+#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:36 en/project_coding-style.ssi:47
#: en/project_coding-style.ssi:59 en/project_coding-style.ssi:70
#: en/project_coding-style.ssi:98 en/project_coding-style.ssi:106
@@ -378,7 +376,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:96
msgid ""
-"Persistence is a common name for different kinds of solutions for saving "
+"'Persistence' is a common name for different kinds of solutions for saving "
"across reboots some, or all, of this run-time evolution of the system. To "
"understand how it could work it could be handy to know that even if the "
"system is booted and run from read-only media, modification to the files and "
@@ -393,15 +391,16 @@ msgid ""
"medium like local storage media, a network share or even a session of a "
"multisession (re)writable CD/DVD. All these media are supported in Debian "
"Live in different ways, and all but the last one require a special boot "
-"parameter to be specified at boot time: #{persistent}#."
+"parameter to be specified at boot time: #{persistence}#."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:100
msgid ""
-"If the boot parameter #{persistent}# is set (and #{nopersistent}# is not "
+"If the boot parameter #{persistence}# is set (and #{nopersistence}# is not "
"set), local storage media (e.g. hard disks, USB drives) will be probed for "
-"persistent volumes during boot. A persistent volume is any of the following:"
+"persistence volumes during boot. A persistence volume is any of the "
+"following:"
msgstr ""
#. type: Plain text
@@ -426,14 +425,14 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:108
msgid ""
-"It is possible to restrict which types of persistent volumes to use by "
+"It is possible to restrict which types of persistence volumes to use by "
"specifying certain boot parameters described in the live-boot(7) man page. "
"The \"identifying labels\" referred to above can be any of the following:"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:110
-msgid "_* #{full-ov}# for full persistent overlays."
+msgid "_* #{full-ov}# for full persistence overlays."
msgstr ""
#. type: Plain text
@@ -453,7 +452,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:118
-msgid "3~ Full persistent overlays"
+msgid "3~ Full persistence overlays"
msgstr ""
#. type: Plain text
@@ -461,7 +460,7 @@ msgstr ""
msgid ""
"By 'full persistence' it is meant that instead of using a tmpfs for storing "
"modifications to the read-only media (with the copy-on-write, COW, system) a "
-"persistent volume is used. For this type of persistence the volume label "
+"persistence volume is used. For this type of persistence the volume label "
"must be #{full-ov}#. This could, for instance, be an ext4 partition on a "
"hard disk or on a usb key created with, e.g.:"
msgstr ""
@@ -521,18 +520,18 @@ msgstr ""
#: en/user_customization-runtime.ssi:151
msgid ""
"A volume with the label #{custom-ov}# can be configured to make arbitrary "
-"directories persistent. The file #{live.persist}#, located on the volume's "
-"filesystem root, controls which directories it makes persistent, and in "
-"which way."
+"directories persistent. The file #{live-persistence.conf}#, located on the "
+"volume's filesystem root, controls which directories it makes persistent, "
+"and in which way."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:153
msgid ""
"How custom overlay mounts are configured is described in full detail in the "
-"live.persist(5) man page, but a simple example should be sufficient for most "
-"uses. Let's say we want to make our home directory and APT cache persistent "
-"in an ext4 filesystem on the /dev/sdb1 partition:"
+"live-persistence.conf(5) man page, but a simple example should be sufficient "
+"for most uses. Let's say we want to make our home directory and APT cache "
+"persistent in an ext4 filesystem on the /dev/sdb1 partition:"
msgstr ""
#. type: Plain text
@@ -541,34 +540,34 @@ msgstr ""
msgid ""
" $ mkfs.ext4 -L custom-ov /dev/sdb1\n"
" $ mount -t ext4 /dev/sdb1 /mnt\n"
-" $ echo \"/home\" >> /mnt/live.persist\n"
-" $ echo \"/var/cache/apt\" >> /mnt/live.persist\n"
+" $ echo \"/home\" >> /mnt/live-persistence.conf\n"
+" $ echo \"/var/cache/apt\" >> /mnt/live-persistence.conf\n"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:164
msgid ""
"Then we reboot. During the first boot the contents of #{/home}# and #{/var/"
-"cache/apt}# will be copied into the persistent volume, and from then on all "
-"changes to these directories will live in the persistent volume. Please note "
-"that any paths listed in the #{live.persist}# file cannot contain white "
-"spaces or the special #{.}# and #{..}# path components. Also, neither #{/"
-"live}# (or any of its sub-directories) nor #{/}# can be made persistent "
-"using custom mounts (for the latter, use the #{full-ov}# type persistence "
-"described above)."
+"cache/apt}# will be copied into the persistence volume, and from then on all "
+"changes to these directories will live in the persistence volume. Please "
+"note that any paths listed in the #{live-persistence.conf}# file cannot "
+"contain white spaces or the special #{.}# and #{..}# path components. Also, "
+"neither #{/live}# (or any of its sub-directories) nor #{/}# can be made "
+"persistent using custom mounts (for the latter, use the #{full-ov}# type "
+"persistence described above)."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:166
msgid ""
-"Several different custom overlay volumes (with their own #{live.persist}# "
-"files) can be used at the same time, but if several volumes make the same "
-"directory persistent, only one of them will be used. If any two mounts are "
-"\"nested\" (i.e. one is a sub-directory of the other) the parent will be "
+"Several different custom overlay volumes (with their own #{live-persistence."
+"conf}# files) can be used at the same time, but if several volumes make the "
+"same directory persistent, only one of them will be used. If any two mounts "
+"are \"nested\" (i.e. one is a sub-directory of the other) the parent will be "
"mounted before the child so no mount will be hidden by the other. Nested "
-"custom mounts are problematic if they are listed in the same #{live.persist}"
-"# file. See the live.persist(5) man page for how to handle that case if you "
-"really need it (hint: you usually don't)."
+"custom mounts are problematic if they are listed in the same #{live-"
+"persistence.conf}# file. See the live-persistence.conf(5) man page for how "
+"to handle that case if you really need it (hint: you usually don't)."
msgstr ""
#. type: Plain text
@@ -580,13 +579,13 @@ msgstr ""
#: en/user_customization-runtime.ssi:170
msgid ""
"Snapshots are collections of files and directories which are not mounted "
-"while running but which are copied from a persistent volume to the system "
+"while running but which are copied from a persistence volume to the system "
"(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The "
"volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive "
"named #{live-sn.cpio.gz}#. A power interruption during run time could lead "
"to data loss, hence, if you have important changes, invoke #{live-snapshot --"
"refresh}# as often as needed. This type of persistence, since it does not "
-"write continuously to the persistent media, is the most flash-based device "
+"write continuously to the persistence media, is the most flash-based device "
"friendly and the fastest of all the persistence systems, but it occupies as "
"much RAM as the size of the uncompressed snapshot."
msgstr ""
@@ -605,19 +604,19 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:176
-msgid "3~ Persistent SubText"
+msgid "3~ Persistence SubText"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:178
msgid ""
-"If a user would need multiple persistent storage of the same type for "
+"If a user would need multiple persistence storage of the same type for "
"different locations or testing, such as #{full-ov-nonwork}# and #{full-ov-"
-"work}#, the boot parameter #{persistent-subtext}# used in conjunction with "
-"the boot parameter #{persistent}# will allow for multiple but unique "
-"persistent media. An example would be if a user wanted to use a persistent "
+"work}#, the boot parameter #{persistence-subtext}# used in conjunction with "
+"the boot parameter #{persistence}# will allow for multiple but unique "
+"persistence media. An example would be if a user wanted to use a persistence "
"partition labeled #{live-sn-subText}# they would use the boot parameters of: "
-"#{persistent}# #{persistent-subtext=subText}#."
+"#{persistence}# #{persistence-subtext=subText}#."
msgstr ""
#. type: Plain text
diff --git a/manual/pot/user_customization-runtime.ssi.pot b/manual/pot/user_customization-runtime.ssi.pot
index 982ed6e..92728c7 100644
--- a/manual/pot/user_customization-runtime.ssi.pot
+++ b/manual/pot/user_customization-runtime.ssi.pot
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-04-08 12:15+0300\n"
+"POT-Creation-Date: 2012-06-03 20:02+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
@@ -17,11 +17,10 @@ msgstr ""
"Content-Transfer-Encoding: 8bit\n"
#. type: Plain text
-#: en/about_manual.ssi:90 en/about_manual.ssi:98 en/about_manual.ssi:106
-#: en/about_manual.ssi:114 en/about_manual.ssi:122 en/about_manual.ssi:130
-#: en/about_manual.ssi:142 en/about_manual.ssi:155 en/about_manual.ssi:168
-#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/about_manual.ssi:195
-#: en/about_manual.ssi:203 en/project_bugs.ssi:60
+#: en/about_manual.ssi:88 en/about_manual.ssi:96 en/about_manual.ssi:104
+#: en/about_manual.ssi:112 en/about_manual.ssi:120 en/about_manual.ssi:128
+#: en/about_manual.ssi:140 en/about_manual.ssi:153 en/about_manual.ssi:166
+#: en/about_manual.ssi:179 en/about_manual.ssi:187 en/project_bugs.ssi:60
#: en/project_coding-style.ssi:30 en/project_coding-style.ssi:40
#: en/project_coding-style.ssi:53 en/project_coding-style.ssi:63
#: en/project_coding-style.ssi:94 en/project_coding-style.ssi:102
@@ -88,11 +87,10 @@ msgid "code{"
msgstr ""
#. type: Plain text
-#: en/about_manual.ssi:94 en/about_manual.ssi:102 en/about_manual.ssi:110
-#: en/about_manual.ssi:118 en/about_manual.ssi:126 en/about_manual.ssi:134
-#: en/about_manual.ssi:151 en/about_manual.ssi:164 en/about_manual.ssi:173
-#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/about_manual.ssi:199
-#: en/about_manual.ssi:207 en/project_bugs.ssi:64
+#: en/about_manual.ssi:92 en/about_manual.ssi:100 en/about_manual.ssi:108
+#: en/about_manual.ssi:116 en/about_manual.ssi:124 en/about_manual.ssi:132
+#: en/about_manual.ssi:149 en/about_manual.ssi:162 en/about_manual.ssi:171
+#: en/about_manual.ssi:183 en/about_manual.ssi:191 en/project_bugs.ssi:64
#: en/project_coding-style.ssi:36 en/project_coding-style.ssi:47
#: en/project_coding-style.ssi:59 en/project_coding-style.ssi:70
#: en/project_coding-style.ssi:98 en/project_coding-style.ssi:106
@@ -378,7 +376,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:96
msgid ""
-"Persistence is a common name for different kinds of solutions for saving "
+"'Persistence' is a common name for different kinds of solutions for saving "
"across reboots some, or all, of this run-time evolution of the system. To "
"understand how it could work it could be handy to know that even if the "
"system is booted and run from read-only media, modification to the files and "
@@ -393,15 +391,16 @@ msgid ""
"medium like local storage media, a network share or even a session of a "
"multisession (re)writable CD/DVD. All these media are supported in Debian "
"Live in different ways, and all but the last one require a special boot "
-"parameter to be specified at boot time: #{persistent}#."
+"parameter to be specified at boot time: #{persistence}#."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:100
msgid ""
-"If the boot parameter #{persistent}# is set (and #{nopersistent}# is not "
+"If the boot parameter #{persistence}# is set (and #{nopersistence}# is not "
"set), local storage media (e.g. hard disks, USB drives) will be probed for "
-"persistent volumes during boot. A persistent volume is any of the following:"
+"persistence volumes during boot. A persistence volume is any of the "
+"following:"
msgstr ""
#. type: Plain text
@@ -426,14 +425,14 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:108
msgid ""
-"It is possible to restrict which types of persistent volumes to use by "
+"It is possible to restrict which types of persistence volumes to use by "
"specifying certain boot parameters described in the live-boot(7) man page. "
"The \"identifying labels\" referred to above can be any of the following:"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:110
-msgid "_* #{full-ov}# for full persistent overlays."
+msgid "_* #{full-ov}# for full persistence overlays."
msgstr ""
#. type: Plain text
@@ -453,7 +452,7 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:118
-msgid "3~ Full persistent overlays"
+msgid "3~ Full persistence overlays"
msgstr ""
#. type: Plain text
@@ -461,7 +460,7 @@ msgstr ""
msgid ""
"By 'full persistence' it is meant that instead of using a tmpfs for storing "
"modifications to the read-only media (with the copy-on-write, COW, system) a "
-"persistent volume is used. For this type of persistence the volume label "
+"persistence volume is used. For this type of persistence the volume label "
"must be #{full-ov}#. This could, for instance, be an ext4 partition on a "
"hard disk or on a usb key created with, e.g.:"
msgstr ""
@@ -521,18 +520,18 @@ msgstr ""
#: en/user_customization-runtime.ssi:151
msgid ""
"A volume with the label #{custom-ov}# can be configured to make arbitrary "
-"directories persistent. The file #{live.persist}#, located on the volume's "
-"filesystem root, controls which directories it makes persistent, and in "
-"which way."
+"directories persistent. The file #{live-persistence.conf}#, located on the "
+"volume's filesystem root, controls which directories it makes persistent, "
+"and in which way."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:153
msgid ""
"How custom overlay mounts are configured is described in full detail in the "
-"live.persist(5) man page, but a simple example should be sufficient for most "
-"uses. Let's say we want to make our home directory and APT cache persistent "
-"in an ext4 filesystem on the /dev/sdb1 partition:"
+"live-persistence.conf(5) man page, but a simple example should be sufficient "
+"for most uses. Let's say we want to make our home directory and APT cache "
+"persistent in an ext4 filesystem on the /dev/sdb1 partition:"
msgstr ""
#. type: Plain text
@@ -541,34 +540,34 @@ msgstr ""
msgid ""
" $ mkfs.ext4 -L custom-ov /dev/sdb1\n"
" $ mount -t ext4 /dev/sdb1 /mnt\n"
-" $ echo \"/home\" >> /mnt/live.persist\n"
-" $ echo \"/var/cache/apt\" >> /mnt/live.persist\n"
+" $ echo \"/home\" >> /mnt/live-persistence.conf\n"
+" $ echo \"/var/cache/apt\" >> /mnt/live-persistence.conf\n"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:164
msgid ""
"Then we reboot. During the first boot the contents of #{/home}# and #{/var/"
-"cache/apt}# will be copied into the persistent volume, and from then on all "
-"changes to these directories will live in the persistent volume. Please note "
-"that any paths listed in the #{live.persist}# file cannot contain white "
-"spaces or the special #{.}# and #{..}# path components. Also, neither #{/"
-"live}# (or any of its sub-directories) nor #{/}# can be made persistent "
-"using custom mounts (for the latter, use the #{full-ov}# type persistence "
-"described above)."
+"cache/apt}# will be copied into the persistence volume, and from then on all "
+"changes to these directories will live in the persistence volume. Please "
+"note that any paths listed in the #{live-persistence.conf}# file cannot "
+"contain white spaces or the special #{.}# and #{..}# path components. Also, "
+"neither #{/live}# (or any of its sub-directories) nor #{/}# can be made "
+"persistent using custom mounts (for the latter, use the #{full-ov}# type "
+"persistence described above)."
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:166
msgid ""
-"Several different custom overlay volumes (with their own #{live.persist}# "
-"files) can be used at the same time, but if several volumes make the same "
-"directory persistent, only one of them will be used. If any two mounts are "
-"\"nested\" (i.e. one is a sub-directory of the other) the parent will be "
+"Several different custom overlay volumes (with their own #{live-persistence."
+"conf}# files) can be used at the same time, but if several volumes make the "
+"same directory persistent, only one of them will be used. If any two mounts "
+"are \"nested\" (i.e. one is a sub-directory of the other) the parent will be "
"mounted before the child so no mount will be hidden by the other. Nested "
-"custom mounts are problematic if they are listed in the same #{live.persist}"
-"# file. See the live.persist(5) man page for how to handle that case if you "
-"really need it (hint: you usually don't)."
+"custom mounts are problematic if they are listed in the same #{live-"
+"persistence.conf}# file. See the live-persistence.conf(5) man page for how "
+"to handle that case if you really need it (hint: you usually don't)."
msgstr ""
#. type: Plain text
@@ -580,13 +579,13 @@ msgstr ""
#: en/user_customization-runtime.ssi:170
msgid ""
"Snapshots are collections of files and directories which are not mounted "
-"while running but which are copied from a persistent volume to the system "
+"while running but which are copied from a persistence volume to the system "
"(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The "
"volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive "
"named #{live-sn.cpio.gz}#. A power interruption during run time could lead "
"to data loss, hence, if you have important changes, invoke #{live-snapshot --"
"refresh}# as often as needed. This type of persistence, since it does not "
-"write continuously to the persistent media, is the most flash-based device "
+"write continuously to the persistence media, is the most flash-based device "
"friendly and the fastest of all the persistence systems, but it occupies as "
"much RAM as the size of the uncompressed snapshot."
msgstr ""
@@ -605,19 +604,19 @@ msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:176
-msgid "3~ Persistent SubText"
+msgid "3~ Persistence SubText"
msgstr ""
#. type: Plain text
#: en/user_customization-runtime.ssi:178
msgid ""
-"If a user would need multiple persistent storage of the same type for "
+"If a user would need multiple persistence storage of the same type for "
"different locations or testing, such as #{full-ov-nonwork}# and #{full-ov-"
-"work}#, the boot parameter #{persistent-subtext}# used in conjunction with "
-"the boot parameter #{persistent}# will allow for multiple but unique "
-"persistent media. An example would be if a user wanted to use a persistent "
+"work}#, the boot parameter #{persistence-subtext}# used in conjunction with "
+"the boot parameter #{persistence}# will allow for multiple but unique "
+"persistence media. An example would be if a user wanted to use a persistence "
"partition labeled #{live-sn-subText}# they would use the boot parameters of: "
-"#{persistent}# #{persistent-subtext=subText}#."
+"#{persistence}# #{persistence-subtext=subText}#."
msgstr ""
#. type: Plain text
diff --git a/manual/pt_BR/user_customization-runtime.ssi b/manual/pt_BR/user_customization-runtime.ssi
index 30b0b38..a5dc96b 100644
--- a/manual/pt_BR/user_customization-runtime.ssi
+++ b/manual/pt_BR/user_customization-runtime.ssi
@@ -130,7 +130,7 @@ other media in addition to CDs; but still, in its default behaviour, it
should be considered read-only and all the run-time evolutions of the system
are lost at shutdown.
-Persistence is a common name for different kinds of solutions for saving
+'Persistence' is a common name for different kinds of solutions for saving
across reboots some, or all, of this run-time evolution of the system. To
understand how it could work it could be handy to know that even if the
system is booted and run from read-only media, modification to the files and
@@ -141,11 +141,12 @@ The data stored on this ramdisk should be saved on a writable persistent
medium like local storage media, a network share or even a session of a
multisession (re)writable CD/DVD. All these media are supported in Debian
Live in different ways, and all but the last one require a special boot
-parameter to be specified at boot time: #{persistent}#.
+parameter to be specified at boot time: #{persistence}#.
-If the boot parameter #{persistent}# is set (and #{nopersistent}# is not
+If the boot parameter #{persistence}# is set (and #{nopersistence}# is not
set), local storage media (e.g. hard disks, USB drives) will be probed for
-persistent volumes during boot. A persistent volume is any of the following:
+persistence volumes during boot. A persistence volume is any of the
+following:
_* a partition, identified by its GPT name.
@@ -156,12 +157,12 @@ _* an image/archive file located on the root of any readable filesystem
this case the file name must also use the containing filesystem as the file
extension, e.g. "<label>.ext4".
-It is possible to restrict which types of persistent volumes to use by
+It is possible to restrict which types of persistence volumes to use by
specifying certain boot parameters described in the live-boot(7) man
page. The "identifying labels" referred to above can be any of the
following:
-_* #{full-ov}# for full persistent overlays.
+_* #{full-ov}# for full persistence overlays.
_* #{custom-ov}# for custom overlays.
@@ -169,11 +170,11 @@ _* #{live-sn}# for full system snapshots.
_* #{home-sn}# for /home snapshots.
-3~ Full persistent overlays
+3~ Full persistence overlays
By 'full persistence' it is meant that instead of using a tmpfs for storing
modifications to the read-only media (with the copy-on-write, COW, system) a
-persistent volume is used. For this type of persistence the volume label
+persistence volume is used. For this type of persistence the volume label
must be #{full-ov}#. This could, for instance, be an ext4 partition on a
hard disk or on a usb key created with, e.g.:
@@ -210,52 +211,53 @@ reboot.
3~ Custom overlays
A volume with the label #{custom-ov}# can be configured to make arbitrary
-directories persistent. The file #{live.persist}#, located on the volume's
-filesystem root, controls which directories it makes persistent, and in
-which way.
+directories persistent. The file #{live-persistence.conf}#, located on the
+volume's filesystem root, controls which directories it makes persistent,
+and in which way.
How custom overlay mounts are configured is described in full detail in the
-live.persist(5) man page, but a simple example should be sufficient for most
-uses. Let's say we want to make our home directory and APT cache persistent
-in an ext4 filesystem on the /dev/sdb1 partition:
+live-persistence.conf(5) man page, but a simple example should be sufficient
+for most uses. Let's say we want to make our home directory and APT cache
+persistent in an ext4 filesystem on the /dev/sdb1 partition:
code{
$ mkfs.ext4 -L custom-ov /dev/sdb1
$ mount -t ext4 /dev/sdb1 /mnt
- $ echo "/home" >> /mnt/live.persist
- $ echo "/var/cache/apt" >> /mnt/live.persist
+ $ echo "/home" >> /mnt/live-persistence.conf
+ $ echo "/var/cache/apt" >> /mnt/live-persistence.conf
}code
Then we reboot. During the first boot the contents of #{/home}# and
-#{/var/cache/apt}# will be copied into the persistent volume, and from then
-on all changes to these directories will live in the persistent
-volume. Please note that any paths listed in the #{live.persist}# file
-cannot contain white spaces or the special #{.}# and #{..}# path
+#{/var/cache/apt}# will be copied into the persistence volume, and from then
+on all changes to these directories will live in the persistence
+volume. Please note that any paths listed in the #{live-persistence.conf}#
+file cannot contain white spaces or the special #{.}# and #{..}# path
components. Also, neither #{/live}# (or any of its sub-directories) nor
#{/}# can be made persistent using custom mounts (for the latter, use the
#{full-ov}# type persistence described above).
-Several different custom overlay volumes (with their own #{live.persist}#
-files) can be used at the same time, but if several volumes make the same
-directory persistent, only one of them will be used. If any two mounts are
-"nested" (i.e. one is a sub-directory of the other) the parent will be
-mounted before the child so no mount will be hidden by the other. Nested
-custom mounts are problematic if they are listed in the same
-#{live.persist}# file. See the live.persist(5) man page for how to handle
-that case if you really need it (hint: you usually don't).
+Several different custom overlay volumes (with their own
+#{live-persistence.conf}# files) can be used at the same time, but if
+several volumes make the same directory persistent, only one of them will be
+used. If any two mounts are "nested" (i.e. one is a sub-directory of the
+other) the parent will be mounted before the child so no mount will be
+hidden by the other. Nested custom mounts are problematic if they are listed
+in the same #{live-persistence.conf}# file. See the live-persistence.conf(5)
+man page for how to handle that case if you really need it (hint: you
+usually don't).
3~ Snapshots
Snapshots are collections of files and directories which are not mounted
-while running but which are copied from a persistent volume to the system
+while running but which are copied from a persistence volume to the system
(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The
volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive
named #{live-sn.cpio.gz}#. A power interruption during run time could lead
to data loss, hence, if you have important changes, invoke #{live-snapshot
--refresh}# as often as needed. This type of persistence, since it does not
-write continuously to the persistent media, is the most flash-based device
+write continuously to the persistence media, is the most flash-based device
friendly and the fastest of all the persistence systems, but it occupies as
much RAM as the size of the uncompressed snapshot.
@@ -264,15 +266,15 @@ works the same as the main snapshot but it is only applied to /home.
Snapshots cannot currently handle file deletion.
-3~ Persistent SubText
+3~ Persistence SubText
-If a user would need multiple persistent storage of the same type for
+If a user would need multiple persistence storage of the same type for
different locations or testing, such as #{full-ov-nonwork}# and
-#{full-ov-work}#, the boot parameter #{persistent-subtext}# used in
-conjunction with the boot parameter #{persistent}# will allow for multiple
-but unique persistent media. An example would be if a user wanted to use a
-persistent partition labeled #{live-sn-subText}# they would use the boot
-parameters of: #{persistent}# #{persistent-subtext=subText}#.
+#{full-ov-work}#, the boot parameter #{persistence-subtext}# used in
+conjunction with the boot parameter #{persistence}# will allow for multiple
+but unique persistence media. An example would be if a user wanted to use a
+persistence partition labeled #{live-sn-subText}# they would use the boot
+parameters of: #{persistence}# #{persistence-subtext=subText}#.
3~ Partial remastering
diff --git a/manual/ro/user_customization-runtime.ssi b/manual/ro/user_customization-runtime.ssi
index 30b0b38..a5dc96b 100644
--- a/manual/ro/user_customization-runtime.ssi
+++ b/manual/ro/user_customization-runtime.ssi
@@ -130,7 +130,7 @@ other media in addition to CDs; but still, in its default behaviour, it
should be considered read-only and all the run-time evolutions of the system
are lost at shutdown.
-Persistence is a common name for different kinds of solutions for saving
+'Persistence' is a common name for different kinds of solutions for saving
across reboots some, or all, of this run-time evolution of the system. To
understand how it could work it could be handy to know that even if the
system is booted and run from read-only media, modification to the files and
@@ -141,11 +141,12 @@ The data stored on this ramdisk should be saved on a writable persistent
medium like local storage media, a network share or even a session of a
multisession (re)writable CD/DVD. All these media are supported in Debian
Live in different ways, and all but the last one require a special boot
-parameter to be specified at boot time: #{persistent}#.
+parameter to be specified at boot time: #{persistence}#.
-If the boot parameter #{persistent}# is set (and #{nopersistent}# is not
+If the boot parameter #{persistence}# is set (and #{nopersistence}# is not
set), local storage media (e.g. hard disks, USB drives) will be probed for
-persistent volumes during boot. A persistent volume is any of the following:
+persistence volumes during boot. A persistence volume is any of the
+following:
_* a partition, identified by its GPT name.
@@ -156,12 +157,12 @@ _* an image/archive file located on the root of any readable filesystem
this case the file name must also use the containing filesystem as the file
extension, e.g. "<label>.ext4".
-It is possible to restrict which types of persistent volumes to use by
+It is possible to restrict which types of persistence volumes to use by
specifying certain boot parameters described in the live-boot(7) man
page. The "identifying labels" referred to above can be any of the
following:
-_* #{full-ov}# for full persistent overlays.
+_* #{full-ov}# for full persistence overlays.
_* #{custom-ov}# for custom overlays.
@@ -169,11 +170,11 @@ _* #{live-sn}# for full system snapshots.
_* #{home-sn}# for /home snapshots.
-3~ Full persistent overlays
+3~ Full persistence overlays
By 'full persistence' it is meant that instead of using a tmpfs for storing
modifications to the read-only media (with the copy-on-write, COW, system) a
-persistent volume is used. For this type of persistence the volume label
+persistence volume is used. For this type of persistence the volume label
must be #{full-ov}#. This could, for instance, be an ext4 partition on a
hard disk or on a usb key created with, e.g.:
@@ -210,52 +211,53 @@ reboot.
3~ Custom overlays
A volume with the label #{custom-ov}# can be configured to make arbitrary
-directories persistent. The file #{live.persist}#, located on the volume's
-filesystem root, controls which directories it makes persistent, and in
-which way.
+directories persistent. The file #{live-persistence.conf}#, located on the
+volume's filesystem root, controls which directories it makes persistent,
+and in which way.
How custom overlay mounts are configured is described in full detail in the
-live.persist(5) man page, but a simple example should be sufficient for most
-uses. Let's say we want to make our home directory and APT cache persistent
-in an ext4 filesystem on the /dev/sdb1 partition:
+live-persistence.conf(5) man page, but a simple example should be sufficient
+for most uses. Let's say we want to make our home directory and APT cache
+persistent in an ext4 filesystem on the /dev/sdb1 partition:
code{
$ mkfs.ext4 -L custom-ov /dev/sdb1
$ mount -t ext4 /dev/sdb1 /mnt
- $ echo "/home" >> /mnt/live.persist
- $ echo "/var/cache/apt" >> /mnt/live.persist
+ $ echo "/home" >> /mnt/live-persistence.conf
+ $ echo "/var/cache/apt" >> /mnt/live-persistence.conf
}code
Then we reboot. During the first boot the contents of #{/home}# and
-#{/var/cache/apt}# will be copied into the persistent volume, and from then
-on all changes to these directories will live in the persistent
-volume. Please note that any paths listed in the #{live.persist}# file
-cannot contain white spaces or the special #{.}# and #{..}# path
+#{/var/cache/apt}# will be copied into the persistence volume, and from then
+on all changes to these directories will live in the persistence
+volume. Please note that any paths listed in the #{live-persistence.conf}#
+file cannot contain white spaces or the special #{.}# and #{..}# path
components. Also, neither #{/live}# (or any of its sub-directories) nor
#{/}# can be made persistent using custom mounts (for the latter, use the
#{full-ov}# type persistence described above).
-Several different custom overlay volumes (with their own #{live.persist}#
-files) can be used at the same time, but if several volumes make the same
-directory persistent, only one of them will be used. If any two mounts are
-"nested" (i.e. one is a sub-directory of the other) the parent will be
-mounted before the child so no mount will be hidden by the other. Nested
-custom mounts are problematic if they are listed in the same
-#{live.persist}# file. See the live.persist(5) man page for how to handle
-that case if you really need it (hint: you usually don't).
+Several different custom overlay volumes (with their own
+#{live-persistence.conf}# files) can be used at the same time, but if
+several volumes make the same directory persistent, only one of them will be
+used. If any two mounts are "nested" (i.e. one is a sub-directory of the
+other) the parent will be mounted before the child so no mount will be
+hidden by the other. Nested custom mounts are problematic if they are listed
+in the same #{live-persistence.conf}# file. See the live-persistence.conf(5)
+man page for how to handle that case if you really need it (hint: you
+usually don't).
3~ Snapshots
Snapshots are collections of files and directories which are not mounted
-while running but which are copied from a persistent volume to the system
+while running but which are copied from a persistence volume to the system
(tmpfs) at boot and which are resynced at reboot/shutdown of the system. The
volume must be labeled #{live-sn}#, and it defaults to a simple cpio archive
named #{live-sn.cpio.gz}#. A power interruption during run time could lead
to data loss, hence, if you have important changes, invoke #{live-snapshot
--refresh}# as often as needed. This type of persistence, since it does not
-write continuously to the persistent media, is the most flash-based device
+write continuously to the persistence media, is the most flash-based device
friendly and the fastest of all the persistence systems, but it occupies as
much RAM as the size of the uncompressed snapshot.
@@ -264,15 +266,15 @@ works the same as the main snapshot but it is only applied to /home.
Snapshots cannot currently handle file deletion.
-3~ Persistent SubText
+3~ Persistence SubText
-If a user would need multiple persistent storage of the same type for
+If a user would need multiple persistence storage of the same type for
different locations or testing, such as #{full-ov-nonwork}# and
-#{full-ov-work}#, the boot parameter #{persistent-subtext}# used in
-conjunction with the boot parameter #{persistent}# will allow for multiple
-but unique persistent media. An example would be if a user wanted to use a
-persistent partition labeled #{live-sn-subText}# they would use the boot
-parameters of: #{persistent}# #{persistent-subtext=subText}#.
+#{full-ov-work}#, the boot parameter #{persistence-subtext}# used in
+conjunction with the boot parameter #{persistence}# will allow for multiple
+but unique persistence media. An example would be if a user wanted to use a
+persistence partition labeled #{live-sn-subText}# they would use the boot
+parameters of: #{persistence}# #{persistence-subtext=subText}#.
3~ Partial remastering
--
live-manual
More information about the debian-live-changes
mailing list