4 ms·

Debian will disable this if they want.

morganvachon 10y ago
But they shouldn't have to. Changing a default, known, long used feature of UNIX-like OSes without any sort of announcement or debate is dangerous and irresponsible. This kind of thing is why I feel the encroachment of systemd into most Linux distros is a bad thing. It's a great system in theory and I am excited about its potential, but it has some extremely egotistical and irresponsible developers who don't give a damn about what they break, as long as they can keep pushing code out without community testing or review to slow them down. Debian was flat out wrong to go with systemd until it reaches a certain level of maturity and stability, but there's no going back now.
- mindslight 10y ago
  I think this is what happens when the "web 2.0" cancer leaks from the casino :/ FWIW "HandleLidSwitch=ignore" is another back-to-normal that will probably save you some walking.
- justinsaccount 10y ago
  > without community testing or review This is a bug report in debian unstable against a bleeding edge version of systemd released 5 days ago.
  - morganvachon 10y ago
    They pushed this "feature" without any advance notice to developers of userland apps like screen and tmux, leaving them to pick up the pieces and figure out what happened. That is irresponsible and reckless. Common sense dictates that when you're going to introduce severe breakage, you give advance warning so it can be properly tested and dealt with. And it's having a negative effect on their own pet distro as well, see this thread: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZNQW72UP36UAFMX53HPFFQTWTQDZVJ3M/ https://lists.fedoraproject.org/archives/list/devel@lists.fe...
    - justinsaccount 10y ago
      No, it's having a negative effect on rawhide which is "the current development version of Fedora". You act like every single systemd user on the planet upgraded to the bleeding edge version of systemd and had this configuration option changed on them overnight.
    - justinsaccount 10y ago
      Oh, and here is your "advanced notice" http://tmux-users.narkive.com/LXp72CHV/pam-support-in-tmux http://tmux-users.narkive.com/LXp72CHV/pam-support-in-tmux
      - morganvachon 10y ago
        That was notice that it would be a compile time option, not set to the unexpected and harmful setting as default.
- jlgaddis 10y ago
  We used to make jokes about Emacs being bloated and how it would eventually be its own operating system, etc. systemd has gotten much closer to that point in a much shorter time.
  - gosub 10y ago
    I would be happy to replace systemd on my system with sys-emacs-d.el

But they shouldn't have to. Changing a default, known, long used feature of UNIX-like OSes without any sort of announcement or debate is dangerous and irresponsible. This kind of thing is why I feel the encroachment of systemd into most Linux distros is a bad thing. It's a great system in theory and I am excited about its potential, but it has some extremely egotistical and irresponsible developers who don't give a damn about what they break, as long as they can keep pushing code out without community testing or review to slow them down. Debian was flat out wrong to go with systemd until it reaches a certain level of maturity and stability, but there's no going back now.

mindslight 10y ago
I think this is what happens when the "web 2.0" cancer leaks from the casino :/ FWIW "HandleLidSwitch=ignore" is another back-to-normal that will probably save you some walking.
justinsaccount 10y ago
> without community testing or review This is a bug report in debian unstable against a bleeding edge version of systemd released 5 days ago.
- morganvachon 10y ago
  They pushed this "feature" without any advance notice to developers of userland apps like screen and tmux, leaving them to pick up the pieces and figure out what happened. That is irresponsible and reckless. Common sense dictates that when you're going to introduce severe breakage, you give advance warning so it can be properly tested and dealt with. And it's having a negative effect on their own pet distro as well, see this thread: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZNQW72UP36UAFMX53HPFFQTWTQDZVJ3M/ https://lists.fedoraproject.org/archives/list/devel@lists.fe...
  - justinsaccount 10y ago
    No, it's having a negative effect on rawhide which is "the current development version of Fedora". You act like every single systemd user on the planet upgraded to the bleeding edge version of systemd and had this configuration option changed on them overnight.
  - justinsaccount 10y ago
    Oh, and here is your "advanced notice" http://tmux-users.narkive.com/LXp72CHV/pam-support-in-tmux http://tmux-users.narkive.com/LXp72CHV/pam-support-in-tmux
    - morganvachon 10y ago
      That was notice that it would be a compile time option, not set to the unexpected and harmful setting as default.
jlgaddis 10y ago
We used to make jokes about Emacs being bloated and how it would eventually be its own operating system, etc. systemd has gotten much closer to that point in a much shorter time.
- gosub 10y ago
  I would be happy to replace systemd on my system with sys-emacs-d.el