SoylentNews is people
SoylentNews
Earlier this week, KDE developer David Edmundson described in his blog how KDE would be tied to logind and timedated but not systemd itself, at least according to his claim that "The init system is one part of systemd that doesn't affect us at all, and any other could be used.".
Later, in the blog comments, he clarifies that starting with plasma 5.5, in 6 months, they'll drop "legacy" support, according to a decision taken in the plasma sprint.
Even if one can only guess why there is no formal announcement, it seems clear - unless somehow there is a shim or emulator, not only for logind but also for timedated, in 6 months KDE will be unusable unless you are running systemd. And the blog entry makes it clear that the plan is to remove more and more functionality from KDE and use systemd instead.
(Score: 2, Interesting) by anti-NAT on Saturday February 21 2015, @05:15AM
The joke of the outrage is that SystemD has been in Fedora since version 15, released in May 2011. As there have been 6 releases since, all including SystemD, clearly the problems the ragers think is going to happen won't. It would have been abandoned by Fedora, or Fedora's users would have abandoned Fedora, if SystemD is as bad as people are making it out to be.
As most people who criticise SystemD repeatedly state falsehoods about it, because they don't actually know what they're talking about (and have no interest in finding out about it), it really says that they're not complaining about SystemD, they're really complaining about change. Technology is always changing, if you can't handle change, go back to pens and pencils.
If the supposed worst happens with SystemD, (a) it can be forked and (b) its API calls are clearly available to be reimplemented.
Nobody is forcing other distributions or software to adopt SystemD or its components - they're doing it because they can see benefits in comparison to their existing methods.
Nobody is forcing you to stay using those distributions if you don't like the direction they're heading either. I've changed distributions plenty of times since 1993 - I've used Slackware, Redhat, Debian, Ubunto, ArchLinux and now use Fedora. It's not hard, and interesting to find out the different ways the same problems are solved.
(Score: 0) by Anonymous Coward on Sunday February 22 2015, @08:40AM
Fedora won't abandon it, because RH needs it for its security wankery sales pits to the MIC.
Fedora seems to always be on the forefront of adopting something "security" related, and/or pushing stuff that is related to same.
Lately there have been a whole lot of RH people screaming, under the guise of Gnome or Wayland devs, "X11 IS NOT SECURE!!!".
Fedora was also on the forefront of adopting SELinux, and it was a massive pain...
And one would suspect that if one traced the lineage of Polkit etc it would lead back to someone on the RH payroll.
But at the same time the Systemd guys manage to add a DNS "client" that is susceptible to cache poisoning. A issue as old as DNS caching, and has known techniques for avoiding...
In essence Fedora is sticking with it because it is "their" project.
Others on the other hand is likely adopting it, or adopted it, back when it was simply a init replacement. These days however it is so much "more". And has a stated goal of reworking the Linux "distro" (more like making them all march in lock step) from the ground up (cramming everything into /usr etc).
(Score: 2) by urza9814 on Monday February 23 2015, @07:31PM
I've had to add a bunch of systemctl commands to my .xinitrc because I couldn't figure out how the hell to get them to start in a predictable order. Network works fine one day, then I upgrade my system and suddenly the services start up in a different order and the network fails on boot...then I update again and it goes back the way it used to be...so now as soon as the system is up I just immediately reboot all the related services in the correct order since SystemD apparently can't figure that out...