You forgot the most important ones.
Unix Error Messages
At the USENIX Association conference in Atlanta recently (Ed: 1985/198
+6)
a contest was held to invent the most humorous/bizarre/etc. UN*X error
+
message of the errno(2) 'EERROR' type. This contest had been tried at
+an
earlier European Users Group meeting, where the winning entry was
ENOTOBACCO - Read on an empty pipe
You get the idea. A partial (alphabetized) list of 'top(?)' entries fr
+om
Atlanta (and from several readers of hp.unix) follows; if your pun/wei
+rdness
tolerance is low, you may want to abandon ship:
EBEFOREI - Invalid syntax
ECHERNOBYL - Core dumped
ECRAY - Program exited before being run
EDINGDONG - The daemon is dead
EFLAT - System needs tuning
EGEEK - Program written by inept Frat member
EIEIO - Here-a-bug, there-a-bug, ....
EIUD - Missing period
ELECTROLUX - Your code could stand to be cleaned up
EMILYPOST - Wrong fork
END.ARMS.CONTROL - Silo overflow
ENOHORSE - Mount failed
ENONSEQUITUR - C program not derived from main(){printf("Hello, world"
+);}
EWATERGATE - Extended tape gap
EWOK - Aliens sighted
EWOK - Your code appears to have been stir-fried
EWOULDBNICE - The feature you want has not been implemented yet
And finally, a sort-of 'period piece':
EMR.ED -
A host is a host,
From coast to coast
And nobody talks to a host that's close,
Unless the host that isn't close
Is busy, hung, or dead.
I would also like this new signal to be supported:
SIGNUKE - Nuclear event occurred (cannot be caught or ignored :-)
:) :) :)
--
Human history becomes more and more a race between education and catastrophe. -- HG Wells
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|