Allright, I may not need devuan gnu/linux in the future since I can choose at installation time the init system on debian.

But it seems the efforts to actually restore the compatibility of some components with sysvinit is from devuan, not debian. May be wrong again.

Those are steps in the right direction. But I stay alert: I know that sysvinit experience could be actually desastrous on debian compared to devuan. Not to mention the debian "default" is systemd: we all know how critical is the choice of the "default" on the long run, that's why I may still go to devuan.

Or post-installation. Basically install sysvinit-core, copy inittab to /etc and reboot (systemd can then be removed/autoremoved/purged according to taste).

One one hand I am thankful for the fact that this guide exist. On the other hand, I am getting strong HHGTTG vibes [1] from them: "you can choose sysvinit as long as you follow a complex set of steps that's likely to go wrong detailed inside a hard-to-find package".

Maybe I'm asking too much, but for me "official" support would mean that I can do it from the installer directly, no terminals and chroots required.

[1] https://www.goodreads.com/quotes/40705-but-the-plans-were-on...