4 ms·
From 2014-06-11 systemd news: > * The support for SysV and LSB init scripts has been removed from the systemd daemon itself. Instead, it is now implemented as
by sverige 8y ago
From 2014-06-11 systemd news:
> * The support for SysV and LSB init scripts has been removed from the systemd daemon itself. Instead, it is now implemented as a generator that creates native systemd units
from these scripts when needed. This enables us to remove a
substantial amount of legacy code from PID 1, following the
fact that many distributions only ship a very small number
of LSB/SysV init scripts nowadays.
At the earliest possible opportunity, systemd removed everything they could that supported alternative init systems. So no, it is not trivial to take a Debian release and make it run SysVinit or OpenRC. In fact, it was so much work that the Devuan devs expended the effort to fork, including setting up a website, mailing lists, IRC channels, a bug-tracker, and all the other infrastructure necessary to maintain a serious, well-supported distro.
And as far as "upstreaming" to Debian, how is Debian upstream for SysVinit or OpenRC? Both of those are separate projects not owned by Debian.
- jhkaghjkga 8y agoSo changing an implementation detail how the support for sysvinit scripts for systemd works means they "removed everything they could"? That's a strange way to put it. And if "apt-get install sysvinit-core" is not trivial for you, then yes, you might need a special distribution doing that for you.
- vbernat 8y ago> So no, it is not trivial to take a Debian release and make it run SysVinit or OpenRC. It is: "apt install sysvinit-core". For some reason, we still carry the burden of maintaining compatibility with many init systems while the "pro-choice" players don't. > And as far as "upstreaming" to Debian, how is Debian upstream for SysVinit or OpenRC? Both of those are separate projects not owned by Debian. Until recently, sysvinit was maintained by Debian.