On Sa, 05.10.24 10:53, Alexander Bokovoy (abokovoy@xxxxxxxxxx) wrote: > > The homed approach would make other things possible too. For example, > > sharing of /home in dual-boot scenarios. Right now a manual setup > > needs to be done, and login details need to be propagated each time, > > but with homed, dual-boot and reinstall are very similar scenarios, > > so if we get one to work, we get the other one for free. > > Can we move systemd-homed configuration and activation into something > that could be explicitly enabled by the administrators? Whether this is > done during installation or post, it still would need to be a concious > step made by admins. It's activated on-demand only. It should not take much resources hence. > Right now systemd-homed is activated on each system without ask for it, > even on systems that do not benefit from its use (see parallel > discussion by Neal). I also see it as a sole contributor to SELinux AVCs > in OpenQA tests we run for FreeIPA use cases. That seems like a bug in the SELinux policy really. Lennart -- Lennart Poettering, Berlin -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
