First, it systemd, not SystemD. Stop spreading lies and disinformation. There is nothing proprietary about systemd. It is 100% open source. It is also even more configurable than really any other init system. You can adjust and configure everything. There is far more flexibility due to its modular design. Its fully backward compatible with SysV init. Poettering has contributed far more code to the open source cause than you could even dream of.
It is 100% open source. It is also even more configurable than really any other init system. You can adjust and configure everything. There is far more flexibility due to its modular design.
And still, it is a piece of shit.
There was never a proper justification for systemd, its proponents presented a couple of tricks it does but never a vision, not even a convincing technical justification for that structural monstrosity.
Systemd was just pushed down everyone's throats and "live with that".
What about documentation? When it comes to systemd, I'm unaware of anything resembling proper documentation.
What I do know is fragmented information from internet forums, but I cannot really say I understand
They infected linux long before they supported systemd. That clusterfuck took 5 years to clean up and still left a taint in the libstdc++ abi that hasn't been removed since.
Well played, RedHat (Score:3, Insightful)
So this is what infecting the Linux ecosystem with systemD is worth. A lot of control, proprietary services, and a very special place at the table.
For the record: fuck systemD and Pottering.
Re: (Score:-1)
I second that. Screw systemd.
Thank you, IBM (Score:0)
I welcome the new IBM overlord.
IBM of today is an entity which fucked up every. single. thing. it touched.
By acquiring RedHat, IBM will fuck up RedHat, and when RedHat is fucked, systemd is fucked too !
What are you waiting for, IBM? Go fuck up RedHat and kill systemd for us, now !
Re: (Score:0)
so where do you go?
Easy: (Score:0)
https://devuan.org
May Poettering burn in hell.
Re: (Score:0)
First, it systemd, not SystemD. Stop spreading lies and disinformation. There is nothing proprietary about systemd. It is 100% open source. It is also even more configurable than really any other init system. You can adjust and configure everything. There is far more flexibility due to its modular design. Its fully backward compatible with SysV init. Poettering has contributed far more code to the open source cause than you could even dream of.
Re: (Score:0)
Fuck systemd.
Re: (Score:0)
It's garbage that locks you into a proprietary configuration. Buggy has root exploits every several months. Fails to shutdown properly.
Re: (Score:0)
It's syndrome D
Re: (Score:0)
It is 100% open source. It is also even more configurable than really any other init system. You can adjust and configure everything. There is far more flexibility due to its modular design.
And still, it is a piece of shit.
There was never a proper justification for systemd, its proponents presented a couple of tricks it does but never a vision, not even a convincing technical justification for that structural monstrosity.
Systemd was just pushed down everyone's throats and "live with that".
What about documentation? When it comes to systemd, I'm unaware of anything resembling proper documentation.
What I do know is fragmented information from internet forums, but I cannot really say I understand
Don't forget gcc-2.96!!!! (Score:0)
They infected linux long before they supported systemd. That clusterfuck took 5 years to clean up and still left a taint in the libstdc++ abi that hasn't been removed since.
Re: (Score:0)
So this is what infecting the Linux ecosystem with systemD is worth. A lot of control, proprietary services, and a very special place at the table.
For the record: fuck systemD and Pottering.
Grow up. Try it.
Re: (Score:2)
So this is what infecting the Linux ecosystem with systemD is worth.
You don't understand. This isn't systemd's fault. It's Trump's. This post may sound stupid but it makes far more sense than what you just wrote.