On Mi, 10.04.19 12:49, Kamil Paral (kparal@xxxxxxxxxx) wrote: > > Hmm, but the installed OS is not 100% the same as the livesys, or is > > it? If not, it should be possible to add a "systemctl disable > > dmraid.service --root=/path/to/os" somewhere, no? > > AFAIK, they are 100% same. There's a hack, check your > /etc/rc.d/init.d/livesys > /etc/rc.d/init.d/livesys-late > They are executed every time during boot, but immediately quit if they > detect they're not running on a Live image (using kernel command line). You > can see them also here: > https://pagure.io/fedora-kickstarts/blob/f30/f/fedora-live-base.ks#_73 > https://pagure.io/fedora-kickstarts/blob/f30/f/fedora-live-base.ks#_232 > They are ugly, I think, and many improvements could be made there. But some > Live image adjustments are possible through them. But those are just > runtime changes for Live environment, they don't affect the installed > system. If anaconda had a post-install phase where it would make > appropriate changes to the installed system (and also ideally removed > itself and those livesys scripts), that would be great, yes. Those scripts, can't we make them part of some RPM btw? I filed a bug about that yesterday: https://bugzilla.redhat.com/show_bug.cgi?id=1698119 These scripts are a bit annoying since they are the only SysV scripts left really (not even LSB!), have no purposes on an installed system and live outside of any RPM ownership and validation. Lennart -- Lennart Poettering, Berlin _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
