[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1066646: live-boot: fails to mount persistence *files* from beside the live medium



Package: live-boot
Version: 1:20230131
Severity: normal

Dear Maintainer,

since the fix_ for #934701_, live boot is no longer considering the
partition mounted e.g. on /run/live/medium even when looking for
persistence partition image files (as opposed to persistence on regular
partitions).

It is my understanding that those would not fall under the case of 

   The devices that are hosting the actual live rootfs should not be
   used for persistence storage since otherwise you might mount a parent
   directory on top of a sub-directory of the same filesystem in one
   union together.

as described in the comment_ in the code that is doing the check, and
thus they could be safely considered. Is it correct, or am I missing
something?

.. _fix: https://salsa.debian.org/live-team/live-boot/-/commit/ce7770b39f38d08bef557b67496c167499c0e3f4
.. _#934701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934701
.. _comment: https://salsa.debian.org/live-team/live-boot/-/blob/ce7770b39f38d08bef557b67496c167499c0e3f4/components/9990-misc-helpers.sh#L1076

My usecase is that I'm running a system with multiple versions of a live
system, each one of which has its own versioned /live directory with
kernel etc. files, filesystem.squashfs *and* a persistence image file.
This used to work up to bullseye, but has stopped working under
bookworm, with the fixed version of live-boot.

Would this be considered a valid usecase?

In case it can be useful, what I'm doing is available online at
https://github.com/Truelite/modian , where the -full-examples reproduce
the issue.

Thanks in advance


Reply to: