Here's a though: try remembering you don't speak for "sysadmins", you speak for yourself.
I think he speaks for sysadmins. If you are using cgroups at the moment you can write scripts for them. It's a mounted filesystem. The change forces you to use systemd for cgroups as only systemd is able to write to cgroups. The argument is: If you don't like systemd implement an alternative that does this for you. Some for kdbus and udev, netlink...
The article is right - it's not Linux as we know it anymore for better or worse.
Re:Systemd redux: The end of Linux
by sandGorgon on Thursday November 20, 2014 @11:25PM
(#8639806)
That is the change that kernel wants, not systemd.
They want to prevent direct access to Cgroups, other than through a single writer. This change is happening regardless of whether you want systemd or not.
You are right. I remembered reading an article from 2013 that gave the impression that the changes where related to systemd and then it shed a different light on the issues (https://lwn.net/Articles/555922/) but it looks like the features are mostly back and in a better shape: http://lwn.net/Articles/601840/
He doesn't speak for sysadmins. I'm a sysadmin, and I love Systemd.
He may speak for some subset of sysadmin, but he certainly does not speak for us all.
> The change forces you to use systemd for cgroups as only systemd is able to write to cgroups. The argument is: If you don't like systemd implement an alternative that does this for you.
And from the looks of it, this has been done: https://cgmanager.linuxcontainers.org/ as reported at http://lwn.net/Articles/618411/
About udev, Linus has had multiple serious complaints about udev maintainership since GregKH passed it to Kay. Don't you recall the async firmware loading issue...