Il giorno mar 1 ago 2023 alle ore 18:03 Manfred Wassmann via Dng <
dng@???> ha scritto:

In short, yes it's possible but there is one caveat which I outlined in
> [1]: once you remove the init-binary running as pid 1 it may be hard to
> reboot. How hard depends on the init-system to be removed. As a rule of
> thumb it will be the harder the more complicated (bloated) it is.
>
> [1] https://lists.dyne.org/lurker/message/20230728.154236.a5a569ff.en.html
>

The above is a legit concern and a correct reasoning, in theory, but:

systemd maintains a compatibility layer with sysvinit, via the initctl
pipe, so when you switch from sysv ---> systemd or vice versa you can
expect shutdown or reboot commands to work as intended;

as for runit, it has it's own implementation of shutdown that is able to
talk to the initctl pipe, so wen you switch from systemd or from sysv to
runit, reboot and shutdown will work as expected;
however when you switch away from runit more steps are required; the
runit-init package only ships symlinks (/sbin/init, reboot, shutdown, halt,
runlevel) while real binaries are shipped in the runit package. So the
runit-init package will be removed in favor of the incoming init, but you
should not remove the runit package yet, and you can reboot with the
following command
# /lib/runit/runit-init 6
After you reboot successfully into the new init, the runit package can be
safely removed.

I'm not sure about operc, but I suspect the Debian/Devuan implementation
still runs on top of sysvinit.
I think an s6-init package is still missing, so reboot will be problematic
in this case.

Lorenzo




> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>