Re: systemd (Subject line fixed as a public service)

On Mon, 20 Jan 2025 17:02:51 -0000 (UTC)
Jim Jackson <jj@franjam.org.uk> wibbled:

On 2025-01-20, Muttley@DastardlyHQ.org <Muttley@DastardlyHQ.org> wrote:

On Sat, 18 Jan 2025 20:00:35 -0000 (UTC)
Jim Jackson <jj@franjam.org.uk> wibbled:

On 2025-01-16, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:

On Thu, 16 Jan 2025 17:17:50 -0000 (UTC), Waldek Hebisch wrote:
>

Rather that vendors can (an will) break compatibility when they want.

>
But they cannot lock Open Source users into their product.
>

And actually systemd is an example of thing that users are essentially
forced to use regardless if they want it or not ...

>
It is one of many choices of init/service-management systems. You have
your choice of distros with or without it.

>
Certainly for headless (no graphics) purposes, it is still comparatively
easy in Debian to replace systemd with the old sysv-init(or alternative
init) stuff. Though I'm not sure for how long that will be true. But you

don't

even need to switches distros.

>
Where do you get all the /etc/rc* files from that init requires?
>

>
Good call. I'd done an upgrade from the previous version of PiOS that
I'd switched from systemd to sysv-init. That upgrade (yes I know it's
not recommended, but it is possible) put systemd back, so when I did the
switch to sysv-init again, the startup files were still in situ!
>
But they appear to be there as the package orphan-sysvinit-scripts
>
https://packages.debian.org/search?keywords=orphan-sysvinit-scripts

Good to know they're available but I wonder how long that'll last?