Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
devices to read-only mode for forensics investigations.
|
|
|
|
a patch from Michael Prokop <mika@grml.org>.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
not a shell function and causes problems for example within live-snapshot.
|
|
|
|
|
|
when toram is used (Closes: #534878).
|
|
#547149).
|
|
|
|
the persistency layer is respected.
|
|
|
|
with 'does not cleanly unmount' problem when using root persistency.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
persistency device.
|
|
|
|
|
|
The patch provides a boot parameter to be used in conjunction with
persistent and allow for multiple but unique persistent media such as
live-sn-subText with boot parameter persistent-subtext=subText.
|
|
|
|
installed.
|
|
persistent=cryptsetup.
In order to determine if a encrypted partition contains a persistent
partition for live-initramfs, we do have to open it and look into it.
Open means, that the user has to provide the passphase (or key).
A user booting a *default* debian-live system on a machine that has
cryptesetup encrypted partitions should not be bothered by *default*
to enter all his passphrases during the boot process. Also,
encrypted persistency is only usefull when the user knows about it
(= the passphrase to access it). Therefore, it's better to by default
ignore persistency on luks devices.
|
|
Thanks to Rui Miguel Bernardo <rui.bernardo.pt@gmail.com> for the report
and for spotting the bug.
|
|
|
|
|
|
newer.
|
|
|
|
|
|
|
|
|