Further testing of live-boot-3xxx lead me to some conclusions and made a script for making it compatible with scripts that depends on existing /live/cow. ('cowsave' see below attached)
Really a hassle btw to find out behaving of live-boot-3!
This is about when using the 'patched' initrd.img:
First: The script -for example- 'cow-save-part' uses these commands assuming there's only one 'notempty' directory existing:
Code: Select all
:for i in $(ls -d /lib/live/mount/persistence/s*); do
if [ -n "$(ls -A "$i" 2> /dev/null)" ]; then
notempty="$i"
fi
done
ln -s "$notempty" /live/cow- The mounted persistence partition as well as...
- The 'home' partition (which I would expect on /lib/live/mount/medium but it isn't)
Similar situation when using savefile, only that mounted persistence is named loop* and the 'home' partition is also mounted in /lib/live/mount/persistence/
The cowsave script works fine for me (it covers also no-persistence, btw) but should be more tested.
If it works for you also, I'd like to know your opinion, two options, I think:
1) run the 'cowsave' script (or whatever you like naming it) at boot, e.g. from /etc/rc.local
(don't worry, it will only run when using live-boot v3, else it does nothing)
2) add the contents of cowsave on top of any script that depends on /live/cow (e.g. remastercow).
As live-boot v3 is the default for latest Debian-live I think it's important to support it.
That doesn't mean that I like it btw
Also included new apt2sfs-new including live-boot-3 support, however, note: it depends on running 'cowsave' first:
Attached: apt2sfs-new_cowsave.tar.gz
Edit: Re-uploaded, cowsave changed only, now creating right symlink /live/image also in case the persistence savefile is in another partition as the 'home' partition.
Edit2: Sorry, again changed cowsave, didn't trust it, only changed the part in case partition containing savefile is another than the 'home' partition.
Fred
. On Intel machines I met problems with my usb wireless adapter Realtek 8187 and 32bit puppies lately... 