Hi, On Sat, Nov 30, 2024 at 07:16:16PM +0100, poc...@homemail.com wrote: > > From: to...@tuxteam.de > > Why all of Debian? As a SysV init user, I, of course, don't > > have (nor had, ever) that package. That one is for systemd > > users wishing some SysV backward compatibility. > > And that "SysV backward compatibility" has been eliminated from systemd
Okay, there is a fundamental misunderstanding here and I'm afraid it's yours. I am going to try one last time. The "SysV backward compatibility" you're talking about is for systemd users to be able to run things that only have sysv init scripts, not systemd unit files. There are no significant packages left in Debian that require it, so it doesn't matter for Debian. Its removal has been a Debian systemd maintainer goal. Separately, there are people *not using systemnd* on Debian. They don't have systemd at all! They do not have the package that you warn is going away. They will therefore be utterly unaffected by that. So, what you keep going on about is a non-event for both groups. > Yes I do know what systemd-sysv is for (I run my own custom distribution). > > * Support for System V service scripts is deprecated and will be > removed in v258. Please make sure to update your software > *now* to include a native systemd unit file instead of a legacy > System V script to retain compatibility with future systemd releases. You are lecturing someone who is not a user of systemd, about what systemd requires its users to do. A piece of software that has a sysv init script keeps working with sysv init no matter if systemd removes support for ice cream on Tuesdays or turns your mother into an aardvark. Such people do not care what systemd does or does not do, because they don't use it! Imagine that! I am genuinely amazed that this concept is so hard to understand. A new low for debian-user discourse. Regards, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
