Anonymous
In previous antixforum topics, I’m certain we have discussed howto (what is necessary) to customize. The “automated way” detail was not discussed, just howto assign custom O/S and release name to replace antiX… and whatall needs to be changed, in multiple places (and within the initramfs content) so that the customization will survive across remaster and/or snapshot operations. Any automation would hinge on (stack upon) running a script which, on-demand, performed the customization steps.
From foggy memory, I recall worrying that there was a sticking point related to performing a snapshot from an already installed-to-disk system. Upon installation to disk, several “live” components are removed… and later, if a snapshot is performed, a “installed-to-live()” routine does retrieve a fresh, current version, copy of those live -related files. Nowadays, the snapshot tool has a feature (must edit config file to enable?) which will PAUSE after the work directory has been populated with files, so that you can (??? unpack initramfs content, customize, repack) before iso-snapshot proceeds to generating the ISO file.
I tried “dpkg -S”
as root[..] and it returned that they didn’t belong to any package
Also from foggy memory: anticapitalista posted to mention “while snapshot is paused, just edit the working directory copies of lsb-release and os-release.” I’m unsure whether that carries over to the “pretty-name” file which winds up populated along with the dynamically-generated during livesession “initrd.out” file.
/live/config (aka “/etc/live/config”)
$ ls /etc/live/config
boot-device cmdline2 distro font lang proc-cmdline virtualbox
cmdline disabled dmesg.out initrd.out pretty-name tsplash