[SCM] live-manual branch, debian, updated. debian/3.0_a9-1-42-gc85f6f4
chals
chals at altorricon.com
Mon Feb 6 22:41:53 UTC 2012
The following commit has been merged in the debian branch:
commit 6d742a44c4393e5769304239109dd5abe42bd2ab
Author: chals <chals at altorricon.com>
Date: Sat Jan 14 18:54:28 2012 +0100
Updating user_basics, Spanish translation.
diff --git a/manual/de/live-manual.ssm b/manual/de/live-manual.ssm
index 8392343..5d96a73 100644
--- a/manual/de/live-manual.ssm
+++ b/manual/de/live-manual.ssm
@@ -9,7 +9,7 @@
:license: Dieses Programm ist freie Software. Sie können es unter den Bedingungen der GNU General Public License, wie von der Free Software Foundation veröffentlicht, weitergeben und/oder modifizieren, entweder gemäss Version 3 der Lizenz oder (nach Ihrer Option) jeder späteren Version.<br><br>Die Veröffentlichung dieses Programms erfolgt in der Hoffnung, dass es Ihnen von Nutzen sein wird, aber OHNE IRGENDEINE GARANTIE, sogar ohne die implizite Garantie der MARKTREIFE oder der VERWENDBARKEIT FÜR EINEN BESTIMMTEN ZWECK. Details finden Sie in der GNU General Public License.<br><br>Sie sollten ein Exemplar der GNU General Public License zusammen mit diesem Programm erhalten haben. Falls nicht, siehe <http://www.gnu.org/licenses/>.<br><br>Der komplette Text der GNU General Public License kann in der Datei /usr/share/common-licenses/GPL-3 gefunden werden.
@date:
- :published: 2012-01-12
+ :published: 2012-01-14
@publisher: Debian Live Projekt <debian-live at lists.debian.org>
diff --git a/manual/en/live-manual.ssm b/manual/en/live-manual.ssm
index 2adb202..f8f094f 100644
--- a/manual/en/live-manual.ssm
+++ b/manual/en/live-manual.ssm
@@ -9,7 +9,7 @@
:license: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.<br><br>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br><br>You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. <br><br>The complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-3 file.
@date:
- :published: 2012-01-12
+ :published: 2012-01-14
@publisher: Debian Live Project <debian-live at lists.debian.org>
diff --git a/manual/en/user_customization-packages.ssi~ b/manual/en/user_customization-packages.ssi~
deleted file mode 100644
index 4ae33f3..0000000
--- a/manual/en/user_customization-packages.ssi~
+++ /dev/null
@@ -1,346 +0,0 @@
-:B~ Customizing package installation
-
-1~customizing-package-installation Customizing package installation
-
-Perhaps the most basic customization of a Debian live system is the selection of packages to be included in the image. This chapter guides you through the various build-time options to customize live-build's installation of packages. The broadest choices influencing which packages are available to install in the image are the distribution and archive areas. To ensure decent download speeds, you should choose a nearby distribution mirror. You can also add your own repositories for backports, experimental or custom packages, or include packages directly as files. You can define your own lists of packages to include, use live-build's predefined lists, use #{tasksel}# tasks, or a combination of all three. Finally, a number of options give some control over apt, or if you prefer, aptitude, at build time when packages are installed. You may find these handy if you use a proxy, want to disable installation of recommended packages to save space, or need to control which versions of
packages are installed via APT pinning, to name a few possibilities.
-
-2~ Package sources
-
-3~ Distribution, archive areas and mode
-
-The distribution you choose has the broadest impact on which packages are available to include in your live image. Specify the codename, which defaults to #{wheezy}# for the Wheezy version of live-build. Any current distribution carried in the Debian archive may be specified by its codename here. (See {Terms}#terms for more details.) The #{--distribution}# option not only influences the source of packages within the archive, but also instructs #{live-build}# to behave as needed to build each supported distribution. For example, to build against the *unstable* release, Sid, specify:
-
-code{
-
- $ lb config --distribution sid
-
-}code
-
-Within the distribution archive, archive areas are major divisions of the archive. In Debian, these are #{main}#, #{contrib}# and #{non-free}#. Only #{main}# contains software that is part of the Debian distribution, hence that is the default. One or more values may be specified, e.g.
-
-code{
-
- $ lb config --archive-areas "main contrib"
-
-}code
-
-Experimental support is available for some Debian derivatives through a #{--mode}# option. By default, this option is set to #{debian}#, even if you are building on a non-Debian system. If you specify #{--mode ubuntu}# or #{--mode emdebian}#, the distribution names and archive areas for the specified derivative are supported instead of the ones for Debian. The mode also modifies live-build behaviour to suit the derivatives.
-
-*{Note:}* The projects for whom these modes were added are primarily responsible for supporting users of these options. The Debian live project, in turn, provides development support on a best-effort basis only, based on feedback from the derivative projects as we do not develop or support these derivatives ourselves.
-
-3~ Distribution mirrors
-
-The Debian archive is replicated across a large network of mirrors around the world so that people in each region can choose a nearby mirror for best download speed. Each of the #{--parent-mirror-*}# options governs which distribution mirror is used at various stages of the build. Recall from {Stages of the build}#stages-of-the-build that the *bootstrap* stage is when the chroot is initially populated by debootstrap with a minimal system, and the *chroot* stage is when the chroot used to construct the live system's filesystem is built. Thus, the corresponding mirror switches are used for those stages, and later, in the *binary* stage, the #{--parent-mirror-binary}# and #{--parent-mirror-binary-security}# values are used, superceding any mirrors used in an earlier stage.
-
-3~distribution-mirrors-build-time Distribution mirrors used at build time
-
-To set the distribution mirrors used at build time to point at a local mirror, it is sufficient to set #{--parent-mirror-bootstrap}#, #{--parent-mirror-chroot-security}# and #{--parent-mirror-chroot-backports}# as follows.
-
-code{
-
- $ lb config --parent-mirror-bootstrap http://localhost/debian/ \
- --parent-mirror-chroot-security http://localhost/debian-security/ \
- --parent-mirror-chroot-backports http://localhost/debian-backports/
-
-}code
-
-The chroot mirror, specified by #{--parent-mirror-chroot}#, defaults to the #{--parent-mirror-bootstrap}# value.
-
-3~ Distribution mirrors used at run time
-
-The #{--parent-mirror-binary*}# options govern the distribution mirrors placed in the binary image. These may be used to install additional packages while running the live system. The defaults employ #{cdn.debian.net}#, a service that chooses a geographically close mirror based on the user's IP number. This is a suitable choice when you cannot predict which mirror will be best for all of your users. Or you may specify your own values as shown in the example below. An image built from this configuration would only be suitable for users on a network where "#{mirror}#" is reachable.
-
-code{
-
- $ lb config --parent-mirror-binary http://mirror/debian/ \
- --parent-mirror-binary-security http://mirror/debian-security/
-
-}code
-
-3~additional-repositories Additional repositories
-
-You may add more repositories, broadening your package choices beyond what is available in your target distribution. These may be, for example, for backports, experimental or custom packages. To configure additional repositories, create #{config/archives/your-repository.list.chroot}#, and/or #{config/archives/your-repository.list.binary}# files. As with the #{--parent-mirror-*}# options, these govern the repositories used in the *chroot* stage when building the image, and in the *binary* stage, i.e. for use when running the live system.
-
-For example, #{config/archives/live.list.chroot}# allows you to install packages from the debian live snapshot repository at live system build time.
-
-code{
-
- deb http://live.debian.net/ sid-snapshots main contrib non-free
-
-}code
-
-If you add the same line to #{config/archives/live.list.binary}#, the repository will be added to your live system's #{/etc/apt/sources.list.d/}# directory.
-
-If such files exist, they will be picked up automatically.
-
-You should also put the GPG key used to sign the repository into #{config/archives/your-repository.key.{binary,chroot}}# files.
-
-*{Note:}* some preconfigured package repositories are available for easy selection through the #{--archives}# option, e.g. for enabling live snapshots, a simple command is enough to enable it:
-
-code{
-
- $ lb config --archives live.debian.net
-
-}code
-
-2~choosing-packages-to-install Choosing packages to install
-
-There are a number of ways to choose which packages live-build will install in your image, covering a variety of different needs. You can simply name individual packages to install in a package list. You can also choose predefined lists of packages, or use APT tasks. And finally, you may place package files in your #{config/}# tree, which is well suited to testing of new or experimental packages before they are available from a repository.
-
-3~package-lists Package lists
-
-Package lists are a powerful way of expressing which packages should be installed. The list syntax supports included files and conditional sections which makes it easy to build lists from other lists and adapt them for use in multiple configurations. You can use predefined package lists, providing in a modular fashion package selections from each of the major desktop environments and some special purpose lists, as well as standard lists the others are based upon. You can also provide your own package lists, or use a combination of both.
-
-*{Note:}* The behaviour of live-build when specifying a package that does not exist is determined by your choice of APT utility. See {Choosing apt or aptitude}#choosing-apt-or-aptitude for more details.
-
-3~ Predefined package lists
-
-The simplest way to use lists is to specify one or more predefined lists with the #{--package-lists}# option. For example:
-
-code{
-
- $ lb config --package-lists "gnome rescue"
-
-}code
-
-The default location for the list files on your system is #{/usr/share/live/build/package-lists/}#. To determine the packages in a given list, read the corresponding file, paying attention to included files and conditionals as described in the following sections.
-
-3~ Local package lists
-
-You may supplement the predefined lists using local package lists stored in #{config/package-lists/}#.
-
-Package lists that exist in this directory need to have a #{.list}# suffix in order to be processed, and then an additional stage suffix, #{.chroot}# or #{.binary}# to indicate which stage the list is for.
-
-*{Note:}* If you don't specify the stage suffix, the list will be used for both stages. Normally, you want to specify #{.list.chroot}# so that the packages will only be installed in the live filesystem and not have an extra copy of the #{.deb}# placed on the media.
-
-3~ Local binary package lists
-
-To make a binary stage list, place a file suffixed with #{.list.binary}# in #{config/package-lists/}#. These packages are not installed in the live filesystem, but are included on the live media under #{pool/}#. You would typically use such a list with one of the non-live installer variants. As mentioned above, if you want this list to be the same as your chroot stage list, simply use the #{.list}# suffix by itself.
-
-3~ Extending a provided package list using includes
-
-The package lists that are included with live-build make extensive use of includes. Refer to these in the #{/usr/share/live/build/package-lists/}# directory, as they serve as good examples of how to write your own lists.
-
-For example, to make a list that includes the predefined #{gnome}# list plus iceweasel, create #{config/package-lists/my.list.chroot}# with the following contents:
-
-code{
-
- #include <gnome>
- iceweasel
-
-}code
-
-3~ Using conditionals inside package lists
-
-Any of the live-build configuration variables stored in #{config/*}# (minus the #{LB_}# prefix) may be used in conditional statements in package lists. Generally, this means any #{lb config}# option uppercased and with dashes changed to underscores. But in practice, it is only the ones that influence package selection that make sense, such as #{DISTRIBUTION}#, #{ARCHITECTURE}# or #{ARCHIVE_AREAS}#.
-
-For example, to install #{ia32-libs}# if the #{--architecture amd64}# is specified:
-
-code{
-
- #if ARCHITECTURE amd64
- ia32-libs
- #endif
-
-}code
-
-You may test for any one of a number of values, e.g. to install #{memtest86+}# if either #{--architecture i386}# or #{--architecture amd64}# is specified:
-
-code{
-
- #if ARCHITECTURE i386 amd64
- memtest86+
- #endif
-
-}code
-
-You may also test against variables that may contain more than one value, e.g. to install #{vrms}# if either #{contrib}# or #{non-free}# is specified via #{--archive-areas}#:
-
-code{
-
- #if ARCHIVE_AREAS contrib non-free
- vrms
- #endif
-
-}code
-
-A conditional may surround an #{#include}# directive:
-
-code{
-
- #if ARCHITECTURE amd64
- #include <gnome-full>
- #endif
-
-}code
-
-The nesting of conditionals is not supported.
-
-3~ Tasks
-
-The Debian Installer offers the user choices of a number of preselected lists of packages, each one focused on a particular kind of system, or task a system may be used for, such as "Graphical desktop environment", "Mail server" or "Laptop". These lists are called "tasks" and are supported by APT through the "Task:" field. You can specify one or more tasks in live-build by putting them in a list in #{config/task-lists/}#, as in the example below.
-
-code{
-
- $ lb config
- $ echo "mail-server file-server" >> config/task-lists/my.list.chroot
-
-}code
-
-The primary tasks available in the Debian Installer can be listed with #{tasksel --list-tasks}# in the live system. The contents of any task, including ones not included in this list, may be examined with #{tasksel --task-packages}#.
-
-3~desktop-and-language-tasks Desktop and language tasks
-
-Desktop and language tasks are special cases that need some extra planning and configuration. Live images are different from Debian Installer images in this respect. In the Debian Installer, if the medium was prepared for a particular desktop environment flavour, the corresponding task will be automatically installed. Thus, there are internal #{gnome-desktop}#, #{kde-desktop}#, #{lxde-desktop}# and #{xfce-desktop}# tasks, none of which are offered in #{tasksel}#'s menu. Likewise, there are no menu entries for tasks for languages, but the user's language choice during the install influences the selection of corresponding language tasks.
-
-When developing a desktop live image, the image typically boots directly to a working desktop, the choices of both desktop and default language having been made at build time, not at run time as in the case of the Debian Installer. That's not to say that a live image couldn't be built to support multiple desktops or multiple languages and offer the user a choice, but that is not live-build's default behaviour.
-
-Because there is no provision made automatically for language tasks, which include such things as language-specific fonts and input-method packages, if you want them, you need to specify them in your configuration. For example, a GNOME desktop image containing support for Japanese might include these tasks:
-
-code{
-
- $ lb config
- $ echo "gnome-desktop desktop standard laptop" >> config/task-lists/my.list.chroot
- $ echo "japanese japanese-desktop japanese-gnome-desktop" >> config/task-lists/my.list.chroot
-
-}code
-
-Since desktop tasks are "internal" tasks, for every desktop flavour task included in the image, the corresponding value, if it differs from the default, "gnome", must be preseeded in the "tasksel/desktop" debconf variable or else tasksel will not recognize and install it. Thus:
-
-code{
-
- $ lb config
- $ echo 'tasksel tasksel/desktop multiselect kde' >> config/preseed/my.preseed.chroot
-
-}code
-
-This parameter can take multiple values, e.g. "lxde xfce" instead of "kde".
-
-2~installing-modified-or-third-party-packages Installing modified or third-party packages
-
-Whilst it is against the philosophy of Debian Live, it may sometimes be necessary to build a Live system with modified versions of packages that are in the Debian repository. This may be to modify or support additional features, languages and branding, or even to remove elements of existing packages that are undesirable. Similarly, "third-party" packages may be used to add bespoke and/or proprietary functionality.
-
-This section does not cover advice regarding building or maintaining modified packages. Joachim Breitner's 'How to fork privately' method from http://www.joachim-breitner.de/blog/archives/282-How-to-fork-privately.html may be of interest, however. The creation of bespoke packages is covered in the Debian New Maintainers' Guide at http://www.debian.org/doc/maint-guide/ and elsewhere.
-
-There are two ways of installing modified custom packages:
-
-_* #{packages.chroot}#
-
-_* Using a custom APT repository
-
-Using #{packages.chroot}# is simpler to achieve and useful for "one-off" customizations but has a number of drawbacks, whilst using a custom APT repository is more time-consuming to set up.
-
-3~ Using #{packages.chroot}# to install custom packages
-
-To install a custom package, simply copy it to the #{config/packages.chroot/}# directory. Packages that are inside this directory will be automatically installed into the live system during build - you do not need to specify them elsewhere.
-
-Packages *{must}* be named in the prescribed way. One simple way to do this is to use #{dpkg-name}#.
-
-Using #{packages.chroot}# for installation of custom packages has disadvantages:
-
-_* It is not possible to use secure APT.
-
-_* You must install all appropriate packages in the #{config/packages.chroot/}# directory.
-
-_* It does not lend itself to storing Debian Live configurations in revision control.
-
-3~ Using an APT repository to install custom packages
-
-Unlike using #{packages.chroot}#, when using a custom APT repository you must ensure that you specify the packages elsewhere. See {Choosing packages to install}#choosing-packages-to-install for details.
-
-Whilst it may seem unnecessary effort to create an APT repository to install custom packages, the infrastructure can be easily re-used at a later date to offer updates of the modified packages.
-
-3~ Custom packages and APT
-
-live-build uses APT to install all packages into the live system so will therefore inherit behaviours from this program. One relevant example is that (assuming a default configuration) given a package available in two different repositories with different version numbers, APT will elect to install the package with the higher version number.
-
-Because of this, you may wish to increment the version number in your custom packages' #{debian/changelog}# files to ensure that your modified version is installed over one in the official Debian repositories. This may also be achieved by altering the live system's APT pinning preferences - see {APT pinning}#apt-pinning for more information.
-
-2~ Configuring APT at build time
-
-You can configure APT through a number of options applied only at build time. (APT configuration used in the running live system may be configured in the normal way for live system contents, that is, by including the appropriate configurations through #{config/includes.chroot/}#.) For a complete list, look for options starting with #{apt}# in the #{lb_config}# man page.
-
-3~choosing-apt-or-aptitude Choosing apt or aptitude
-
-You can elect to use either #{apt}# or #{aptitude}# when installing packages at build time. Which utility is used is governed by the #{--apt}# argument to #{lb config}#. Choose the method implementing the preferred behaviour for package installation, the notable difference being how missing packages are handled.
-
-_* #{apt}#: With this method, if a missing package is specified, the package installation will fail. This is the default setting.
-
-_* #{aptitude}#: With this method, if a missing package is specified, the package installation will succeed.
-
-3~ Using a proxy with APT
-
-One commonly required APT configuration is to deal with building an image behind a proxy. You may specify your APT proxy with the #{--apt-ftp-proxy}# or #{--apt-http-proxy}# options as needed, e.g.
-
-code{
-
- $ lb config --apt-http-proxy http://proxy/
-
-}code
-
-3~ Tweaking APT to save space
-
-You may find yourself needing to save some space on the image media, in which case one or the other or both of the following options may be of interest.
-
-If you don't want to include APT indices in the image, you can omit those with:
-
-code{
-
- $ lb config --apt-indices false
-
-}code
-
-This will not influence the entries in /etc/apt/sources.list, but merely whether /var/lib/apt contains the indices files or not. The tradeoff is that APT needs those indices in order to operate in the live system, so before performing #{apt-cache search}# or #{apt-get install}#, for instance, the user must #{apt-get update}# first to create those indices.
-
-If you find the installation of recommended packages bloats your image too much, you may disable that default option of APT with:
-
-code{
-
- $ lb config --apt-recommends false
-
-}code
-
-The tradeoff here is that if you don't install recommended packages for a given package, that is, "packages that would be found together with this one in all but unusual installations" (Debian Policy Manual, section 7.2), some packages that you actually need may be omitted. Therefore, we suggest you review the difference turning off recommends makes to your packages list (see the #{binary.packages}# file generated by #{lb build}#) and re-include in your list any missing packages that you still want installed. Alternatively, if you find you only want a small number of recommended packages left out, leave recommends enabled and set a negative APT pin priority on selected packages to prevent them from being installed, as explained in {APT pinning}#apt-pinning.
-
-3~ Passing options to apt or aptitude
-
-If there is not an #{lb config}# option to alter APT's behaviour in the way you need, use #{--apt-options}# or #{--aptitude-options}# to pass any options through to your configured APT tool. See the man pages for #{apt}# and #{aptitude}# for details.
-
-3~apt-pinning APT pinning
-
-For background, please first read the #{apt_preferences(5)}# man page. APT pinning can be configured either for build time, or else for run time. For the former, create #{config/chroot_apt/preferences}#. For the latter, create #{config/includes.chroot/etc/apt/preferences}#.
-
-Let's say you are building a Wheezy live system but need all the live packages that end up in the binary image to be installed from Sid at build time. You need to add Sid to your APT sources and pin it so that only the packages you want are installed from it at build time and all others are taken from the target system distribution, Wheezy. The following will accomplish this:
-
-code{
-
- $ echo "deb http://mirror/debian sid main" > config/archives/sid.list.chroot
- $ cat >> config/chroot_apt/preferences <<END
- Package: live-boot live-boot-initramfs-tools live-config live-config-sysvinit
- Pin: release n=sid
- Pin-Priority: 600
-
- Package: *
- Pin: release n=sid
- Pin-Priority: 1
- END
-
-}code
-
-*{Note:}* Wildcards can be used in package names (e.g. *{Package: live-*}*) with Apt version 0.8.14 or higher. This means that it works with Wheezy using:
-
-code{
-
-$ lb config --distribution wheezy
-
-}code
-
-Negative pin priorities will prevent a package from being installed, as in the case where you do not want a package that is recommended by another package. Suppose you are building an LXDE image using #{--package-lists lxde}# option, but don't want the user prompted to store wifi passwords in the keyring. This list includes #{gdm}#, which depends on #{gksu}#, which in turn recommends #{gnome-keyring}#. So you want to omit the recommended #{gnome-keyring}# package. This can be done by adding the following stanza to #{config/chroot_apt/preferences}#:
-
-code{
-
- Package: gnome-keyring
- Pin: version *
- Pin-Priority: -1
-
-}code
diff --git a/manual/es/live-manual.ssm b/manual/es/live-manual.ssm
index 8d9c5f8..f92c15e 100644
--- a/manual/es/live-manual.ssm
+++ b/manual/es/live-manual.ssm
@@ -9,7 +9,7 @@
:license: Este programa es software libre: puede ser redistribuido y/o modificado bajo los términos de la GNU General Public License publicada por la Free Software Foundation, bien de la versión 3 de la Licencia, o (a su elección) cualquier versión posterior. <br><br> Este programa se distribuye con la esperanza de que sea útil, pero SIN NINGUNA GARANTÍA, incluso sin la garantía implícita de COMERCIALIZACIÓN o IDONEIDAD PARA UN PROPÓSITO PARTICULAR. Consulte la GNU General Public License para más detalles. <br><br> Debería haber recibido una copia de la General Public License GNU junto con este programa. Si no, vea http://www.gnu.org/licenses/. <br><br> El texto completo de la GNU Licencia Pública General se pueden encontrar en /usr/share/common-licenses/GPL-3
@date:
- :published: 2012-01-12
+ :published: 2012-01-14
@publisher: Debian Live Project <debian-live at lists.debian.org>
diff --git a/manual/es/user_basics.ssi b/manual/es/user_basics.ssi
index eb95496..785fd62 100644
--- a/manual/es/user_basics.ssi
+++ b/manual/es/user_basics.ssi
@@ -254,14 +254,15 @@ code{
2~building-hdd Crear una imagen HDD
-La siguiente secuencia de comandos creará una imagen HDD básica que
-contendrá sólo el sistema estándar de Debian sin X.org. Es adecuada para el
-arranque desde dispositivos USB, discos duros USB y otros dispositivos de
-almacenamiento portátil. Normalmente, se puede utilizar para este propósito
-una imagen ISO híbrida, pero es posible que la BIOS no maneje adecuadamente
-las imágenes híbridas. También es interesante una imagen HDD si se desea
-utilizar el espacio restante en los medios de almacenamiento para una
-partición con persistencia.
+Crear una imagen HDD es similar a una de tipo ISO híbrida en todos los
+aspectos, con la diferencia de que hay que especificar #{-b hdd}# y de que
+el nombre de la imagen final es #{binary.img}# que se puede copiar en medios
+ópticos. Es adecuada para el arranque desde dispositivos USB, discos duros
+USB y otros sistemas de almacenamiento portátil. Normalmente, se puede
+utilizar para este propósito una imagen ISO híbrida, pero es posible que la
+BIOS no maneje adecuadamente las imágenes híbridas. También es interesante
+una imagen HDD si se desea utilizar el espacio restante en los medios de
+almacenamiento para una partición con persistencia.
Nota: si se ha creado una imagen ISO híbrida con el ejemplo anterior, se
tendrá que limpiar el directorio de trabajo con el comando #{lb clean}# (ver
diff --git a/manual/fr/live-manual.ssm b/manual/fr/live-manual.ssm
index 97e33ea..7761e9a 100644
--- a/manual/fr/live-manual.ssm
+++ b/manual/fr/live-manual.ssm
@@ -9,7 +9,7 @@
:license: Ce programme est un logiciel libre; vous pouvez le redistribuer ou le modifier suivant les termes de la Licence Générale Publique GNU telle que publiée par la Free Software Foundation: soit la version 3 de cette licence, soit (à votre gré) toute version ultérieure.<br><br>Ce programme est distribué dans l’espoir qu’il vous sera utile, mais SANS AUCUNE GARANTIE: sans même la garantie implicite de COMMERCIALISABILITÉ ni d’ADÉQUATION À UN OBJECTIF PARTICULIER. Consultez la Licence Générale Publique GNU pour plus de détails.<br><br>Vous devriez avoir reçu une copie de la Licence Générale Publique GNU avec ce programme ; si ce n’est pas le cas, consultez http://www.gnu.org/licenses/. <br><br>Le texte complet de la Licence Générale Publique GNU peut être trouvé dans le fichier / usr/share/common-licenses/GPL-3
@date:
- :published: 2012-01-12
+ :published: 2012-01-14
@publisher: Debian Live Project <debian-live at lists.debian.org>
diff --git a/manual/it/live-manual.ssm b/manual/it/live-manual.ssm
index 4fd19df..dccb7b3 100644
--- a/manual/it/live-manual.ssm
+++ b/manual/it/live-manual.ssm
@@ -9,7 +9,7 @@
:license: Questo programma è software libero: è possibile ridistribuirlo e modificarlo secondo i termini della GNU General Public License come pubblicata dalla Free Software Foundation, sia la versione 3 della licenza o (a scelta) una versione successiva.<br><br>Questo programma è distribuito nella speranza che possa essere utile, ma SENZA ALCUNA GARANZIA, nemmeno la garanzia implicita di COMMERCIABILITÀ o IDONEITÀ PER UN PARTICOLARE SCOPO. Vedere la GNU General Public License per ulteriori dettagli.<br><br>Si dovrebbe aver ricevuto una copia della GNU General Public License con questo programma. In caso contrario, vedere http://www.gnu.org/licenses/. <br><br>Il testo completo della GNU General Public License può essere trovato nel file /usr/share/common-licenses/GPL-3.
@date:
- :published: 2012-01-12
+ :published: 2012-01-14
@publisher: Debian Live Project <debian-live at lists.debian.org>
diff --git a/manual/po/de/live-manual.ssm.po b/manual/po/de/live-manual.ssm.po
index 9129633..dcb1ab6 100644
--- a/manual/po/de/live-manual.ssm.po
+++ b/manual/po/de/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-01-12 08:28-0400\n"
+"POT-Creation-Date: 2012-01-14 18:46+0100\n"
"PO-Revision-Date: 2011-04-23 14:15+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -48,7 +48,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-01-12\n"
+" :published: 2012-01-14\n"
msgstr ""
#. type: Plain text
diff --git a/manual/po/es/live-manual.ssm.po b/manual/po/es/live-manual.ssm.po
index a46b33f..ecf9233 100644
--- a/manual/po/es/live-manual.ssm.po
+++ b/manual/po/es/live-manual.ssm.po
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-01-12 08:28-0400\n"
+"POT-Creation-Date: 2012-01-14 18:46+0100\n"
"PO-Revision-Date: 2011-03-12 08:00-0000\n"
"Last-Translator: José Luis Zabalza and Carlos Zuferri «chals» "
"<jlz.3008 at gmail.com> <chals at altorricon.com\n"
@@ -53,7 +53,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-01-12\n"
+" :published: 2012-01-14\n"
msgstr ""
#. type: Plain text
diff --git a/manual/po/es/user_basics.ssi.po b/manual/po/es/user_basics.ssi.po
index fee46ea..30b5675 100644
--- a/manual/po/es/user_basics.ssi.po
+++ b/manual/po/es/user_basics.ssi.po
@@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
"POT-Creation-Date: 2012-01-12 08:28-0400\n"
-"PO-Revision-Date: 2011-11-02 20:28+0100\n"
+"PO-Revision-Date: 2012-01-14 18:42+0100\n"
"Last-Translator: José Luis Zabalza and Carlos Zuferri «chals» "
"<jlz.3008 at gmail.com> <chals at altorricon.com>\n"
"Language-Team: Debian live Spanish translation team <debian-live at lists."
@@ -716,14 +716,15 @@ msgid ""
"space on the media for some purpose, such as a persistence partition, you "
"need an HDD image."
msgstr ""
-"La siguiente secuencia de comandos creará una imagen HDD básica que "
-"contendrá sólo el sistema estándar de Debian sin X.org. Es adecuada para el "
-"arranque desde dispositivos USB, discos duros USB y otros dispositivos de "
-"almacenamiento portátil. Normalmente, se puede utilizar para este propósito "
-"una imagen ISO híbrida, pero es posible que la BIOS no maneje adecuadamente "
-"las imágenes híbridas. También es interesante una imagen HDD si se desea "
-"utilizar el espacio restante en los medios de almacenamiento para una "
-"partición con persistencia."
+"Crear una imagen HDD es similar a una de tipo ISO híbrida en todos los "
+"aspectos, con la diferencia de que hay que especificar #{-b hdd}# y de que "
+"el nombre de la imagen final es #{binary.img}# que se puede copiar en medios "
+"ópticos. Es adecuada para el arranque desde dispositivos USB, discos duros "
+"USB y otros sistemas de almacenamiento portátil. Normalmente, se puede "
+"utilizar para este propósito una imagen ISO híbrida, pero es posible que la "
+"BIOS no maneje adecuadamente las imágenes híbridas. También es interesante "
+"una imagen HDD si se desea utilizar el espacio restante en los medios de "
+"almacenamiento para una partición con persistencia."
#. type: Plain text
#: en/user_basics.ssi:150
diff --git a/manual/po/fr/live-manual.ssm.po b/manual/po/fr/live-manual.ssm.po
index 069b9b4..8497b10 100644
--- a/manual/po/fr/live-manual.ssm.po
+++ b/manual/po/fr/live-manual.ssm.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-01-12 08:28-0400\n"
+"POT-Creation-Date: 2012-01-14 18:46+0100\n"
"PO-Revision-Date: 2011-06-19 16:32+0200\n"
"Last-Translator: Carlos Zuferri «chals» <chals at altorricon.com>\n"
"Language-Team: <debian-live at lists.debian.org>\n"
@@ -49,7 +49,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-01-12\n"
+" :published: 2012-01-14\n"
msgstr ""
#. type: Plain text
diff --git a/manual/po/it/live-manual.ssm.po b/manual/po/it/live-manual.ssm.po
index d71477f..1fb3a45 100644
--- a/manual/po/it/live-manual.ssm.po
+++ b/manual/po/it/live-manual.ssm.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-01-12 08:28-0400\n"
+"POT-Creation-Date: 2012-01-14 18:46+0100\n"
"PO-Revision-Date: 2011-03-11 10:33+0100\n"
"Last-Translator: skizzhg <skizzhg at gmx.com>\n"
"Language-Team: Italian <tp at lists.linux.it>\n"
@@ -49,7 +49,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-01-12\n"
+" :published: 2012-01-14\n"
msgstr ""
#. type: Plain text
diff --git a/manual/po/pt_BR/live-manual.ssm.po b/manual/po/pt_BR/live-manual.ssm.po
index ebe1f93..f3dd5b0 100644
--- a/manual/po/pt_BR/live-manual.ssm.po
+++ b/manual/po/pt_BR/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-01-12 08:28-0400\n"
+"POT-Creation-Date: 2012-01-14 18:46+0100\n"
"PO-Revision-Date: 2010-10-22 07:52-0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -45,7 +45,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-01-12\n"
+" :published: 2012-01-14\n"
msgstr ""
#. type: Plain text
diff --git a/manual/po/ro/live-manual.ssm.po b/manual/po/ro/live-manual.ssm.po
index 089fac8..e86d3af 100644
--- a/manual/po/ro/live-manual.ssm.po
+++ b/manual/po/ro/live-manual.ssm.po
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual 2.0.0\n"
-"POT-Creation-Date: 2012-01-12 08:28-0400\n"
+"POT-Creation-Date: 2012-01-14 18:46+0100\n"
"PO-Revision-Date: 2010-10-23 00:04+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -46,7 +46,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-01-12\n"
+" :published: 2012-01-14\n"
msgstr ""
#. type: Plain text
diff --git a/manual/pot/live-manual.ssm.pot b/manual/pot/live-manual.ssm.pot
index 998a752..6239c25 100644
--- a/manual/pot/live-manual.ssm.pot
+++ b/manual/pot/live-manual.ssm.pot
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: live-manual VERSION\n"
-"POT-Creation-Date: 2012-01-12 08:28-0400\n"
+"POT-Creation-Date: 2012-01-14 18:46+0100\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"
@@ -45,7 +45,7 @@ msgstr ""
#, no-wrap
msgid ""
"@date:\n"
-" :published: 2012-01-12\n"
+" :published: 2012-01-14\n"
msgstr ""
#. type: Plain text
diff --git a/manual/pt_BR/live-manual.ssm b/manual/pt_BR/live-manual.ssm
index 2adb202..f8f094f 100644
--- a/manual/pt_BR/live-manual.ssm
+++ b/manual/pt_BR/live-manual.ssm
@@ -9,7 +9,7 @@
:license: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.<br><br>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br><br>You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. <br><br>The complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-3 file.
@date:
- :published: 2012-01-12
+ :published: 2012-01-14
@publisher: Debian Live Project <debian-live at lists.debian.org>
diff --git a/manual/ro/live-manual.ssm b/manual/ro/live-manual.ssm
index 2adb202..f8f094f 100644
--- a/manual/ro/live-manual.ssm
+++ b/manual/ro/live-manual.ssm
@@ -9,7 +9,7 @@
:license: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.<br><br>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br><br>You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. <br><br>The complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-3 file.
@date:
- :published: 2012-01-12
+ :published: 2012-01-14
@publisher: Debian Live Project <debian-live at lists.debian.org>
--
live-manual
More information about the debian-live-changes
mailing list