To read all comments associated with this story, please click here.
heh, stuff like this always makes me think of that classical unix printer error: "printer on fire".
its a very old error message in computing terms, from when printers used ink ribbons and write heads.
basically the heads where sometimes cleaned in alcohol or something similar.
so, if you take a newly cleaned write head, stick it next to a ream of paper, and then have the printer jam.
this would then all heat up, and one could very well guess what would happen next.
so the programmers put in code that would put those very words on screen if the printer port sent a signal that would indicate a jammed paper.
then it was up to the sysadmin if he would grab the fire extinguisher, or some frozen hot dogs for the bonfire
that, and order up a new printer...
Edited 2008-08-03 00:46 UTC




Member since:
2008-07-01
NetBSD manuals sometimes are funny. For example:
"crime does not pay"
from sgimips/crime(4)
"You can tune a file system, but you can't tune a fish." from tunefs(8)
"Data loss is possible on busy systems with baud rates greater than 300." from amiga/ser(4)
"Bugs? You crazy, man?!?" from robots(6), BUGS section
"Currently it does not support running X. It can however coexist well enough with grf0 to make possible running X the old way, but be warned, you cannot switch screens while in X and when quitting it, it seems to hang. Switching a screen then will bring up the text console. As always, we apologise for the inconvenience." from amiga/amidisplaycc(4)
There is certainly more, but I don't remember them now...