SoylentNews is people
SoylentNews
The spreading of systemd continues, now actively pushed by themselves unto other projects, like tmux:
"With systemd 230 we switched to a default in which user processes started as part of a login session are terminated when the session exists (KillUserProcesses=yes).
[...] Unfortunately this means starting tmux in the usual way is not effective, because it will be killed upon logout."
It seems methods already in use (daemon, nohup) are not good for them, so handling of processes after logout has to change at their request and as how they say. They don't even engange into a discussion about the general issue, but just pop up with the "solution". And what's the "reason" all this started rolling? dbus & GNOME coders can't do a clean logout so it must be handled for them.
Just a "concidence" systemd came to the rescue and every other project like screen or wget will require changes too, or new shims like a nohup will need to be coded just in case you want to use with a non changed program. Users can probably burn all the now obsolete UNIX books. The systemd configuration becomes more like a fake option, as if you don't use it you run into the poorly programmed apps for the time being, and if they ever get fixed, the new policy has been forced into more targets.
Seen at lobsters 1 & 2 where some BSD people look pissed at best. Red Hat, please, just fork and do you own thing, leaving the rest of us in peace. Debian et al, wake up before RH signed RPMs become a hard dependency.
(Score: 3, Interesting) by JNCF on Monday May 30 2016, @04:54PM
The relevant excerpt from OP's link about Red Hat aiming for complexity (emphasis original, to show questions):
Do you think the Red Hat model would apply equally well to other areas of software?
Red Hat's model works because of the complexity of the technology we work with. An operating platform has a lot of moving parts, and customers are willing to pay to be insulated from that complexity.
I don't think you can take one finite element - like Apache - and make a business out of it [using our model]. You need product complexity.
I'm amazed how open they are about this obvious incentive that their business model creates. It seems like the sort of thing you wouldn't want to shout from the rooftops, if you were in the business of making open source software more complex than necessary. They don't say that they make anything more complex than necessary, but they spell out a motive quite clearly.