[ale] Kernel panic

[Joe Knapka]

Emil Man wrote:

> Joe,
>
> Mind if use the fallowing as a signature on my outgoing e-mails?? That 
> is hilarious! GPLv3 it PLEASE!
>
Feel free.  However, I gleaned this wonderful insight by about two minutes
of searching the kernel source using LXR <http://lxr.linux.no/>, so it's 
probably
worth what you're paying for it :-)

-- JK

> Emil
>
>
> 2006/2/14, Joe Knapka < jknapka at kneuro.net <mailto:jknapka at kneuro.net>>:
>
>
>     A kernel panic invariably printks the words "Kernel panic:" on the
>     console.  The difference
>     between a "panic" and an "oops" is that a panic is a situation that is
>     forseen, but which we
>     cannot deal with, such as not being able to free any RAM, or not
>     being
>     able to mount
>     the root filesystem. Both of those are situations that kernel
>     developers
>     can forsee and
>     reasonably plan for, even if the plan is just to say, "screw this, I
>     give up". OTOH an
>     "oops" is something really horrid that should never happen if the
>     universe is in good
>     health, like kernel data structures being corrupt.  In general an oops
>     is more cause for
>     concern than a panic, I'd say.
>
>     -- JK
>
>
>     _______________________________________________
>     Ale mailing list
>     Ale at ale.org <mailto:Ale at ale.org>
>     http://www.ale.org/mailman/listinfo/ale
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Ale mailing list
>Ale at ale.org
>http://www.ale.org/mailman/listinfo/ale
>