Dear Maintainer,
If I create live/config.conf.d/custom.conf inside a Trixie live medium/iso tree with, for example, the following single line:
LIVE_USERNAME='mycustomuser'
...my LIVE_USERNAME parameter does not get picked up by live-config as it does when doing the same to a Bookworm live medium. Meanwhile, the live-config manpage for Trixie still lists live/config.conf.d/* as a valid path, so I would normally expect my config and its params to get picked up.
In init-config.sh, we currently assume that all live media are mounted inside (/usr)/lib/live/mount. This is true and valid as of Bookworm:
> user@debian:~$ grep ^VERSION_CODENAME /etc/os-release && grep 'medium' /proc/mounts
> VERSION_CODENAME=bookworm
> /dev/sr0 /run/live/medium iso9660 ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8 0 0
> /dev/sr0 /usr/lib/live/mount/medium iso9660 ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8 0 0
However, Trixie live images only seem to be mounted in /run/live:
> user@debian:~$ grep ^VERSION_CODENAME /etc/os-release && grep 'medium' /proc/mounts
> VERSION_CODENAME=trixie
> /dev/sr0 /run/live/medium iso9660 ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8 0 0
> user@debian:~$ grep 'lib' /proc/mounts
> user@debian:~$
One can of course work around this by simply placing configs in $rootfs/etc/live instead, but both scenarios are supposed to work.
Adding mountpoints starting with /run/live/medium to init-config.sh appears to resolve the issue for me. If paths starting with (/usr)/lib/live/mount/medium are no longer used by Debian live media at all, they can probably be removed at some point, but I am not sure about that, so my attached suggested patch retains them for now.
Thanks.
Best regards
Aka Sikrom