RTFA: http://www.youtube.com/watch?v=uvlzkdxad-A&eurl=ht…

Pluto is attacked by a Disneyland tourist. Pluto returned with another park employee who talked with the woman, and Pluto left the scene. Everything appeared to be settled peacefully.

Via boingboing. Totally hilarious.

RTFA: http://www.miguelcarrasco.net/miguelcarrasco/2006/…

Nos. 2, 4, 5, 6, 8, 9, and 10 do not show any kind of crash. Those are normal messages. Note a couple of them are too blurry to read, so they might even be BSD or even OSX in diagnostics mode.

#1 looks like SVGAlib crashed, implying bad third-party software, but that’s not what a kernel panic (linux itself crashing) looks like.

#3 again, looks like some third-party software crashed. Linux is doing exactly what it ought to, prompting to launch a recovery (”diagnostics”) console

#7 isn’t even Linux. That’s what Windows looks like when it crashes, my friend.

As for those listed at the beginning of this comment…

#9 and #10 are perfectly normal. That’s what DS Linux looks like after a successful boot, and #10 shows LILO saying it successfully loaded the kernel.

# 2, 4, 5, 6 are too blurry to read. They appear to be normal kernel messages during boot. I can’t even confirm whether 5 is Linux.

#7 displays an inability to access the drive it’s configured to access. Either bad configuration - which is user error - or hardware problems, which is not a problem. Either way, it does not show a single fatal error - the picture shows a successful boot.

The bonus crash image looks like some kid was trying to demo his software and it segfaulted. His fault (bad code), not a Linux crash.

About a year late to the lulz, but this is a totally hilarious collection of “linux crash” images. The comic gold is really in the comments, most of which are just like the one above. As I’m currently battling to build a heavily patched 2.6.18 kernel on potentially unstable, poor-selling 2003-era server hardware, I would have some real pictures to share…