Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
representations.
|
|
|
|
|
|
|
|
* This finally enables one of the most requested feature to exclude
things like disk caches and temporary files from the persistence
images in order to speed things up and saves precious writes of flash
based storages.
This works at boot by bind mounting tmpfs clones of paths listed on
"/etc/live-persistence.binds".
|
|
* This finally enables one of the most requested feature to exclude
things like disk caches and temporary files from the snapshots, just
by editing "/etc/live-snapshot.exclude_list".
This only works for cpio targets and for squashfs creations.
|
|
* Added new way to call "persistent" at boot:
"persistent=nofiles" will skip the scan for image files in block
device and it will only search for partition labels.
|
|
* This finally enables "live-rw" partition persistence, yes it works, it
is still ugly and slow, but make it work first and let optimize it
later, hopefully in one of the next commits.
To rush test it, 'mkfs.ext2 -L "live-rw" /dev/XhdX' on a qemu drive
and reboot the live with "persistent" on.
|
|
* When "/etc/live-snapshot.list" is present, all standard files and
directories listed there are saved on shutdown.
Now it saves them only if they are modified, and also handles
dangling symbolic links. This beaviour will be gentle to live-systems
upgrades on the same hardware since new unmodified to-be-snapshotted files
will be no more overwritten by old unnecessary saved cruft.
It still does not handle removal of deleted files.
|
|
* This is one of a series of interventions that means to be gentle to
debian-live builders and to persistence users; the rationale is that
if a file is present on the rootfs it does not need to be overwritten
from scratch since its presence means either a live-helper
configuration at build time or a persistent/snapshot at run time.
|
|
* This is one of a series of interventions that means to be gentle to
debian-live builders and to persistence users; the rationale is that
if a file is present on the rootfs it does not need to be overwritten
from scratch since its presence means either a live-helper
configuration at build time or a persistent/snapshot at run time.
|
|
|
|
live-functions.
|
|
* Although is really fine to have checks for unboud variables, this
limits also included code, where unbound variables could be used as
feature. Set LIVE_SNAPSHOT_CHECK_UNBOUND to have it on again in your
test runs.
|
|
|
|
* Another clean-up and speed up in the ugly persistance/snapshot code.
|
|
* Quoting a variable could do miracles :-)
|
|
|
|
* "break=<phase>" boot option, previously lead to the overrided panic
function which shows a huge bug message info, which in that particular
case is misleading, since the "dropping to a shell" is wanted.
|
|
|
|
|
|
|
|
Redirect stderr to /dev/null, otherwise we'll get
"stdin: error 0" for some partitions during bootup.
|
|
|
|
|
|
|
|
|
|
* Handle the case in which an user is present but the default user could not
be created (e.g. when configuring another user at build time in the
chroot). If the default user could not be created or assigned, disable
autologins (which previously just fails leaving without console login
capabilities), and propagate that information to the scripts thinking that a
default user will always be available.
Note for live-helper documentation: The latter case could leave the system
accessible only if root password is set in other ways or via ssh rsa/dsa
passwordless accesses.
|
|
|
|
|
|
|
|
|
|
|
|
'swapon' boot parameter. Thanks to Joseph Rawson <umeboshi3@gmail.com> for bringing it up.
|
|
|
|
|
|
try to assume it from the extension of the imagefile we have found. Thanks to Jordi Pujol <jordi_pujol@telefonica.net> (Closes: #460456).
|
|
|