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: 1, Troll) by pvanhoof on Tuesday May 31 2016, @10:21AM
To change my world view it would help if the debate around systemd wasn't one big ad hominem against Lennart. Just skipping the entries that are 99% about Lennart is or would be a daytime job. I specifically said that about that he can be evil as a sarcasm. But look oh look. The word Lennart falls and everybody is up in arms. As if he's the only developer behind systemd, as if the technical merits aren't what is important.
Your criticism of systemd becoming a behemoth is what should be debated, yes. But not whether you like or dislike Lennart. However - systemd as a project, might be a sort of in a monorepo (just like most BSDs are developed). But by itself it's quite modularly done: multiple processes, multiple binaries and you can enable and disable compilation and installation of them. That doesn't sound to me like a behemoth or monolithic design. The choice of storing a large set of components and tools in a single repository is indeed something I don't lilke myself.
I don't think it will last very long like that. I think that eventually the project will split up into multiple smaller ones. But time will tell.
(Score: 2) by Scruffy Beard 2 on Tuesday May 31 2016, @07:28PM
When the same name keeps coming up in software that simply makes your system work better when removed, you start to treat any new code by the person with suspicion.
I have "fixed" glitchy audio by removing pulseaudio. I have seen IPv6 auto-configuration "just work" without network- manager, but not with.
I don't think the init part of systemd has actually bitten me in the ass yet; but I do find auto-mounting drives under the permissions of the currently active user annoying.
(Score: 2) by Zz9zZ on Tuesday May 31 2016, @09:55PM
Thanks for a good reply :) Being human there will always be some who turn to personal attacks for one reason or another. I've read numerous complaints about Torvalds and Poettering, so its just something that happens when a person gets enough visibility.
I hope you're right and sysd gets pared down, but I won't hold my breath.
~Tilting at windmills~