3 ms·
Linux use cases tend to be servers where user interaction is unexpected at 3AM? No one around to make a choice, so automate a choice. IMO despite the standout
by ieoei9jjd 7y ago
Linux use cases tend to be servers where user interaction is unexpected at 3AM? No one around to make a choice, so automate a choice.
IMO despite the standout behavior, I prefer my software to deal with itself.
Systems designed to wait for user input end up having design choices intent on keeping a user using them.
Software is just a tool. Not a lifestyle. Set and forget this shit as much as possible
- hvidgaard 7y agoIf the alternative is simply killing a process or crashing the kernel, then surely a better approach would be to suspend the offending process and call a handle that does something. If you want that something to restart the machine, fine. You want it to notify the administrator, fine.
- pmontra 7y agoThere is the use case of android phones. One of the answers to the OP is about that case. It sends that Google developed a user space process to monitor those events https://lkml.org/lkml/2019/8/5/1121 https://lkml.org/lkml/2019/8/5/1121 From that reply it seems that Facebook implemented something similar, I guess for their servers.
- jcelerier 7y ago> Linux use cases tend to be servers where user interaction is unexpected at 3AM? No one around to make a choice, so automate a choice. Even if it's a small percentage of the overall "computing" population, there are still millions of people running Linux on the desktop (roughly 2% out of 3.2 billion people using internet makes for 64 million - a large european country). It's 64 million of people for which this behaviour is a pain in the arse.