Hi,
On 10/20/26 7:42 AM, Marc Haber wrote:
My gut feeling tells me to depend on systemd-sysv as that one is the one
setting the symlink from /sbin/init to systemd, but that seems kind of
wrong for me since it has "sysv" in the name, the package description
doesn't suggest that it is a package THIS central, and I don't know
whether a, for example, dracut-based initramfs will care where /sbin/
init points to at all.
It's the correct approach IMO.
Frankly, no one reads the package description of systemd-sysv. The only
users who are ever confronted with this package are the ones who want to
uninstall it for some reason, for the rest it's just one of twenty magic
systemd components you don't need to understand (and that it's not a
component is something you don't need to understand either).
If dracut builds an initramfs that doesn't work with non-systemd pid1,
then dracut needs a dependency on systemd-sysv as well. "Doesn't work"
includes "starts an incompletely installed systemd despite the user
selecting a different pid1", because the result is going to be an
unusable system -- such a system would, for example, not have the
systemd NSS modules.
Simon
