At Fri, 28 Feb 2014 14:28:55 -0300, Claudio Freire wrote:
On Fri, Feb 28, 2014 at 2:23 PM, Takashi Iwai email@example.com wrote:
Hence, the only proposal that is needed assuming that .conf works as one would assume (I tried systemd's documentation and found little of use - for the amount of documentation it has, it's horribly structured to say the least), if it works like that, then yast needs an easy-to-use config option for users to switch. That's all.
But how would you start YaST if you can't boot properly at all? You can't choose no matter how it's easy-to-use. No boot, no dice.
Save buggy firmware, I don't see how that can happen. If you see your laptop suspends when you close the lid, you keep the lid open till you changed the setting. There's no rocket science involved, my sister would be able to figure that out.
Buggy firmware is another matter altogether. That would require some kernel-line-level switch I guess (like brokenmodules).
No, you missed the whole point. Suppose you set up logind in that way and boot a machine with the closed lid. Then it doesn't boot fully. It goes suspend immediately instead. That's the problem. It's no bug of firmware. It's just logind.
So, again, how you would change the setup if you can't boot? You can't assume that the boot parameter can be changed, too. Some EFI loader doesn't allow it. Or, the machine is booted up remotely via WoL. So, we can't assume to open the lid physically.
Remember that this can be introduced just by a systemd package update. Then you may have no chance to change the setup before falling into such a situation (or are you changing /etc/logind.conf at each systemd update?).
Yes, this is a corner case. But disallowing such a basic operation like booting is a showstopper. That's why I've been suggesting to consider the default policy very carefully.