🚀 go-pugleaf

In article <45...@apple.Apple.COM>, j...@Apple.COM (John Peterson) writes:
> 
> >>>Given all the weird messages in the machine, what about the error messages
> >>>that get printed from time to time?  I've seen some really bad ones.
> >>>
> >>>I'd have to nominate UNIX's "Not a TTY" and RSTS/E's "?Program lost, sorry"
> >>
> >>I nominate Unix's "Intruder Alert!" and Pick's "This error cannot occur"
> >>	- Brian
> > 
> > I add to the list something BSD 4.3 talk has given me a few times:
> >   "You don't exist. Go away."
> > 
> 
> To this I would add the Unix Mail error if the passwd file is trashed:
> 
> 	No mail for ubluit


UNIX is absolutely chock full of neat messages. There was
one that apparently made it onto a T-Shirt at one of the
USEnix conferences. The picture is of a small bird hanging
from a parachute, and a plane going down in flames. The
caption was:

	"Awk! Bailing out near line 3"

(In case you don't recognize this, "awk" is a
pattern-matching language. Why "AWK"? That's the initials
of the three guys who wrote it - Aho, Weinberger and
Kernigan!)


Another favorite, "Can't grok <string>" I believe this was
"lex"? Maybe "yacc"? ("LEX" is the Lexical analyser generator
program. "YACC" is "Yet Another Compiler Compiler").
Anyways, "grok" hasd found its way into the UNIX lexicon
as a general "I don't understand" lament.