On 2/26/2014 5:58 AM, Robert Milasan wrote:
On Wed, 26 Feb 2014 11:39:03 +0100 Ruediger Meier firstname.lastname@example.org wrote:
On Wednesday 26 February 2014, Raymond Wooninck wrote:
On Tuesday 25 February 2014 20:18:36 Claudio Freire wrote:
Possibly not common, but I've done it. And the whole concept of using a raspberry pi as a server is similar.
Isn't systemd's behavior disableable?
No. This is a built-in feature which can not be switched on or off by the user.
Is this a bad joke? It's really not possible to disable suspend on lid close? But hopefully it's still possible to disable suspend completely?
robert@viper:/etc/systemd> cat logind.conf |grep Lid #HandleLidSwitch=suspend #LidSwitchIgnoreInhibited=yes
Isn't this the way to disable suspend on lid close in systemd?
And just to be clear, this can be done remotely from a serial console, CORRECT? For example, interactively add init=/bin/sh to the boot prompt in grub or syslinux, then from the shell edit the config file, then reboot? Plymouth or bootsplash or some other crap doesn't prevent it?
Oh wait... what laptop has a bios capable of serial console redirection? They would have to either have an expensive ip-kvm hooked up, or require and expensive hands-on visit.
Using a laptop as a server is rarely something someone does as a first choice. The point is, what is the excuse for removing a functionality, a dimension of flexibility, when all the people writing unix and linux have spent decades working so hard *pointedly* to make everything in the system so agnostic?
And for that matter, old laptops and netbooks are perfect little routers and special purpose servers. They're not good for anything else after a little while. Who has any right to tell anyone else they should not do that? It's also an always-handy emergency measure that shouldn't just stop being available one day.