> What I don't like, and completely disagree with, is systemd not working with the community they directly effect to reduce disruption. > Rather than turning a

> What I don't like, and completely disagree with, is systemd not working with the community they directly effect to reduce disruption. > Rather than turning around and requiring everyone to change, they could have said, "Sorry, we're making changes, here are some preliminary patches that could help." > Or a timeline for a breaking change, wherein they can negotiate with others. But they did exactly that. They contacted the tmux mainteners and asked if some modifications would be possible to accomodate the new option (see poettering comment here: run things as child of systemd --user or just register a separate PAM session). If I remember correctly, it would not even have been the first special case in tmux ; there already is one for OSX. The discussion was actually progressing nicely until the anti-systemd flooded it. I remember seeing posts in a lot of place urging people to comment on the bug report with specious arguments. The whole thing was kind of upsetting.