4 ms·
Why does such a feature have to be safe? It's for an edge case where something is misbehaving badly, and your only alternative is a reboot. Why shouldn't the us
by AnIdiotOnTheNet 8y ago
Why does such a feature have to be safe? It's for an edge case where something is misbehaving badly, and your only alternative is a reboot. Why shouldn't the user be able to do this as long as they accept the risk?
> Linux is all about enabling people
Since we're talking about the kernel, I agree for the most part. Which makes it all the more annoying that "reboot" (and sometimes even that doesn't work and you have to smother the system with a pillow) is the only option in this circumstance. I can overwrite disks and memory at will, destroying who knows what data, but I can't kill a useless hung process because it might be unsafe?
Admittedly I am ignorant of the details of the kernel implementation, but I have difficulty believing that there is nothing that can be done.
- ddingus 8y agoSay your kernel panics 10 minutes later, due to an unplanned state caused by ripping the process out of the table. What then? Stuck mount, or unplanned, immediate restart? See the dilemma? This way, you can keep working, save what may be super important, and then restart.