Stories
Slash Boxes
Comments

SoylentNews is people

posted by cmn32480 on Monday May 30 2016, @06:44AM   Printer-friendly
from the fed-up-with-the-UNIX-take-over dept.

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.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by pvanhoof on Monday May 30 2016, @10:24PM

    by pvanhoof (4638) on Monday May 30 2016, @10:24PM (#352791) Homepage

    The systemd developers should do exactly and precisely what they want to do. And absolutely nothing more. If the BSD guys want a form of systemd, then it's up to them to make a systembsd. Or a bsdsystemd. Or b-system-d. Or my fucking god how much I wouldn't care about the recursive acronym that they'd come up with (actually, I would. For the laughs).

    Just like Devuan. I just don't care about the ideology: make it good. Make it worth. Prove yourself. Be the best code. And then I will care.

    Oh and if you as a user want to use FreeBSD: men. That's fantastic for you. I'm so happy for you. Waw. Great. You have freedom. Good that we provide you with it. Now if you want to influence those systems: you better get yourself ready to make the fucking best. Because imagine the shit you see here on soylentnews and slashdot: you'll get all of it. From the nitwits. Constantly. And you better have some arguments. You better be right. Meanwhile, you better be an experimenter who can be wrong at the same time. You better figure out how that can be.

    You better be. It's fucking hard over here.

  • (Score: 0) by Anonymous Coward on Tuesday May 31 2016, @04:57AM

    by Anonymous Coward on Tuesday May 31 2016, @04:57AM (#352944)

    only retards want anything to do with systemd, go preach to systemd conf or the assholes at redhat and debian