What if, instead of using SysVInit and symlinking systemd compatibility, you made a systemd compatible replacement suite that was transparent to applications depending on it?
So, have your "keep everything simple and only doing one thing" philosophy, but integrate it into a suite of tools that can be installed so as to fully be compatible with systemd (maybe throw in sysvinit commands as acceptable as well so that people with scripts or habits from either system will feel at home).
Or is this waaay out of the realm of possibilities?
It just seems like a decent solution to SysVInit vs Systemd, as everything is progressing towards Systemd, but a few people have issue with it, so the best of both worlds should perhaps convince people to move towards an alternate which has the benefits of both Systemd and SysVInit?
Right now you sort of have that but you get stuff like this:
Or failure to open / install due to arcane detection not picking up systemd as running.
Anyways. Just a thought, as in 5-10 years I'm thinking it's just going to get worse, so you're better off trying to come up with a solution that people can move TO, rather than compromises that only satisfy those clinging to the previous generation of solutions (which is fine, but probably won't work forever, unfortunately).
So, have your "keep everything simple and only doing one thing" philosophy, but integrate it into a suite of tools that can be installed so as to fully be compatible with systemd (maybe throw in sysvinit commands as acceptable as well so that people with scripts or habits from either system will feel at home).
Or is this waaay out of the realm of possibilities?
It just seems like a decent solution to SysVInit vs Systemd, as everything is progressing towards Systemd, but a few people have issue with it, so the best of both worlds should perhaps convince people to move towards an alternate which has the benefits of both Systemd and SysVInit?
Right now you sort of have that but you get stuff like this:
Code:
$ sudo systemctl edit libvirtdSystem has not been booted with systemd as init system (PID 1). Can't operate.Failed to connect to bus: Host is downAnyways. Just a thought, as in 5-10 years I'm thinking it's just going to get worse, so you're better off trying to come up with a solution that people can move TO, rather than compromises that only satisfy those clinging to the previous generation of solutions (which is fine, but probably won't work forever, unfortunately).
Statistics: Posted by 0x6A7232 — Sat Apr 06, 2024 8:29 pm