“This is Part 1 in a two-part series on system panics. In this column, Michael Lucas talks about how to prepare a FreeBSD system in case of a panic. In the next column, he’ll talk about what to do when the worst happens.” Read the article at ONLamp.com.
FreeBSD: System Panics, Preparing for the Worst
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Very good article. It’s very true that the FreeBSD developers need a stack trace to help you in the event of a crash; otherwise, they don’t have a clue as to what caused it. I find the occurence of kernel panics extreamly low. I’ve never personally even witnessed one. It’s refreshing to see articles about something new rather than more articles about how to install FreeBSD or how to use cvsup. Those topics are already very well documented in the FreeBSD Handbook.
SARCASM
I didn’t realize that BSD includes its own version of the ‘blue screen of death’. Cool.
I was convinced by the *nix community that only Microsoft included this feature in their NT kernel – because they are so ‘innovative’.
I’ve heard that Linux even comes with an option for creating corrupted file systems too. Wicked.
/SARCASM
The FreeBSD Foundation is now accepting <a href=”http://www.freebsdfoundation.org/#donations“>donations on-line.