Hi, On Sat, Nov 30, 2024 at 01:31:12PM +0100, poc...@homemail.com wrote: > You did not comprehend what I posted.
I think it is you who are having problems reading. > I am on the systemd mail list. > They have dropped all sysV support. > The only way you'll have init script support is if you rip out systemd. Yes, that is what is being said: it is still possible to run Debian without systemd. People are doing it. There are package maintainers that wish to let people do it. Surprise! It's a funny old world. > Since debian is using systemd for their init system debian will have > to come into the here and now. Have you been living under a rock for ten years? The only reason why systemd is able to drop their svsv init script support is *because* Debian has been ready to also do so for a long time! Nothing operates in a vacuum. There are multiple Debian developers who are also systemd developers. They have been working on the goal to make everything in Debian have a native systemd service unit for a *long* time and we've been at that stage for some time already. There is no "coming into the here and now". We are here already because of work done in part by Debian. However it is also separately true that many packages still have a sysv init script that their maintainers support for the purposes of having it work without systemd. Though I have no interest in doing that personally. What you seem to not understand is that it has been Debian policy for *years* for packages to have systemd unit files, but it has not been policy for packages to get rid of any existing or contributed sysv init scripts. That is optional. There's plenty of users who do need to "get into the here and now" (as evidenced by this thread), but Debian itself has been there for a full release cycle at least. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
