> Maybe, but Debian policy reserves the right to break your programs in future updates, right? I'm pretty certain packages wouldn't see a change such as removi

> Maybe, but Debian policy reserves the right to break your programs in future updates, right? I'm pretty certain packages wouldn't see a change such as removing sysvinit support files unless you upgrade to a new major version (i.e. upgrade from Buster to Bullseye). In that scenario, sure, all bets are off. But in that scenario you could also just find the package missing too, so no amount of sysvinit scripts will you if the binary itself is gone. > If you just want to use the most common thing with everything being easily packaged, why would you be using Debian rather than, say, Windows? Wat? A pretty basic Debian Buster box I setup recently has close to 200 systemd unit files from just 24 Debian packages. Are you seriously suggesting that I should remove systemd, install... some other declarative service manager, and then write/find appropriate unit files for all of those services? > The things that traditionally set Debian apart from Windows are the same things that set something like Devuan apart from modern Debian, IME. I'm glad you made sure to classify that as your opinion.