Thought I'd toss in my
for fun.
Most of my hardware isn't compatable with Linux, so I've got stories...
Quote:
|
If you have, say, bad RAM, there's not very much the OS can do about it.
|
One of my problems is bad RAM, so it's a case of suffer at the webbed feet of Tux or the claws of MS. Linux crashes less often than Windows once I tweak a bunch of config files.
Here's a summary of the last crash Linux had:
Had this been WinXP, this would have been a BSOD for sure.
I was downloading a rather big file (a DVD's ISO's size but it was just an archive), so since the download wasn't hogging RAM or CPU I decided to play a full screen solitare game I like while I waited. This game uses very little CPU & RAM, so it's no hog of resources and can usually multitask with other programs.
Keyword: "usually". It froze. No response to mouse or keyboard commands (F9 is a boss key in this program, and should have killed it) and the display blocked up and distorted.
Great: I'd downloaded 547 MB of the file.
BUT all of the lights and indicators on my hardware stated the download was chugging along like nothing happened.
If I attempt to CTRL-ALT-Backspace, I'll kill the download and have to start over. (This was not a BT or any kind of resumable download).
I thought up the solution. Should you have a fullscreen freeze, here's a trick.
1. Hit CTRL-ALT-F2 to switch to a terminal.
2. use the "ps -A" command to get a list of running processes.
3. use "kill ####" to kill the frozen process.
4. Hit CTRL-ALT-F7 to return to the GUI with the offending process gone.
Got my file, and got around a full screen freeze.
