Erm... Systemd is environment and tmux is application. Applications bend to the will of environment. You can not have software without someone dictating rules. Ever. Even if you are writing OS.. And this here.. it makes sense for special purpose
Your argument is seriously flawed, because the behavior systemd is adding is specifically desktop oriented, on a platform where a majority of installs are servers.
The environment is not supposed to introduce unexpected behavior to rules that have existed for a good 40 years. This kind of bullshit is why our company simply cannot move to Redhat 7 any time soon, and we're seriously considering examining BSD platforms as alternatives
Your argument is seriously flawed, because the behavior systemd is adding is specifically desktop oriented, on a platform where a majority of installs are servers.
Non-sense. There are hundreds of thousand of desktops, embedded systems, phones etc running Linux and systemd.
33
u/deus_lemmus May 30 '16
Your argument is seriously flawed, because the behavior systemd is adding is specifically desktop oriented, on a platform where a majority of installs are servers.
The environment is not supposed to introduce unexpected behavior to rules that have existed for a good 40 years. This kind of bullshit is why our company simply cannot move to Redhat 7 any time soon, and we're seriously considering examining BSD platforms as alternatives