4 ms·

I think that you are missing the point. I was quite happy without systemd. What work has to be picked up really? You are trying to make it sound we could not li

I think that you are missing the point. I was quite happy without systemd. What work has to be picked up really? You are trying to make it sound we could not live without systemd and we must replace the systems. If you want to write a better init system, go for it. Many people tried and succeeded none of them became the standard for linux (partially because there are no standards in linux). https://unix.stackexchange.com/questions/5877/what-are-the-pros-cons-of-upstart-and-systemd https://unix.stackexchange.com/questions/5877/what-are-the-p... As I said in other comments, if you want to replace inis scripts with systemd format service descriptors I will support your efforts becuase using shell script is broken. If you in the making of replacing init with something better also replace logging, ntp, dns, dhcp and a bunch of more then I will say no. This is exactly what systemd does. Rewriting rock solid, CPU efficient code with something shaky and CPU intensive. No thanks. >>> And none of the alternatives seem to really get away from the bash script paradigm. Factually incorrect. There are many init alternatives that got away from the shell script paradigm. Including SMF in Solaris. https://www.thegeekdiary.com/a-beginners-guide-to-service-management-facility-smf-in-solaris/ https://www.thegeekdiary.com/a-beginners-guide-to-service-ma...

AsyncAwait 7y ago
> I was quite happy without systemd. Good for you then. I am sure you were happy with X11's rotting core & didn't need Wayland in your life, you also likely weren't the one having to maintain its decades old codebase. > If you want to write a better init system, go for it. Am personally happy with systemd, thanks, if you're not, why don't you go ahead and write a better one, instead of complaining every time systemd's name is mentioned? > This is exactly what systemd does. Rewriting rock solid, CPU efficient code with something shaky and CPU intensive. That doesn't seem factual. systemd is a system manager, useful even after the system is booted up, I think people need to understand that first, it's not just an init system, because many modern services fit an event driven model these days. It's written in C and can run fine on tiny embedded systems. > Factually incorrect. There are many init alternatives that got away from the shell script paradigm. Including SMF in Solaris. Yeah, and launchd on macOS, by which systemd was literally inspired by, we're talking about Linux here, since that's where systemd runs, at least I was.

AsyncAwait 7y ago

> I was quite happy without systemd. Good for you then. I am sure you were happy with X11's rotting core & didn't need Wayland in your life, you also likely weren't the one having to maintain its decades old codebase. > If you want to write a better init system, go for it. Am personally happy with systemd, thanks, if you're not, why don't you go ahead and write a better one, instead of complaining every time systemd's name is mentioned? > This is exactly what systemd does. Rewriting rock solid, CPU efficient code with something shaky and CPU intensive. That doesn't seem factual. systemd is a system manager, useful even after the system is booted up, I think people need to understand that first, it's not just an init system, because many modern services fit an event driven model these days. It's written in C and can run fine on tiny embedded systems. > Factually incorrect. There are many init alternatives that got away from the shell script paradigm. Including SMF in Solaris. Yeah, and launchd on macOS, by which systemd was literally inspired by, we're talking about Linux here, since that's where systemd runs, at least I was.