The only solution I see with systemd is rewriting it completely in Rust...
Announcement
Collapse
No announcement yet.
systemd Clocks In At More Than 1.2 Million Lines
Collapse
X
-
Originally posted by nomadewolf View PostSystemD is not perfect.
But it works surpringly well, for the huge behemoth it is...
Usually i find that running it is way better than the alternative. Because there's no real alternative to it.
Init systems, alternative:OpenRC, runit, upstart
Service managers: daemontools, runit has (compatible with daemontools btw) service supervision tools, freedt.
There are some language extensions, which can do service monitoring/managing (Perl's Ubic or Python's Circus for example). Some Linux distro even ran Python executable instead of SysV init executable and all it's services were managed by Python scripts.
It's very funny how it's 'easier' to re-invent huge behemoth of a wheel..
- Likes 1
Comment
-
Originally posted by Cape View PostMaking GTK in C was a mistake.
I agree that the current Glib and GTK interfaces are complex but having the whole stuff in C is not as bad as you say. It's a very valid technical choice.
Comment
-
Originally posted by tuxd3v View PostThis monster. will implode some day..
Seems that the Linux Community lost focus, KISS, objectivity.
In a pair of years...unfortunately, we will have to create a real init system... to correct the mistakes of almost a decade of craziest things that have been allowed..
Linux choice of init has always been choice of what broken I wish to have today. Maybe by 5.2 kernel we will have chance at long last of a init system that functions correctly.
Comment
-
Originally posted by arokh View Post
So basically, you used Linux for 23 years and you're still a complete noob? In any case, I fully support your move to Devuan. It's absolutely the best place for you and like minded people.
Noob is this systemd shit. And I thrive on change. When the change is for the better, which isn't the case with systemd.
- Likes 2
Comment
Comment