The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] made up errno contest, at an early USENIX
Date: Thu, 2 Oct 2014 21:46:26 +1000	[thread overview]
Message-ID: <20141002114626.GA548@www.oztivo.net> (raw)
In-Reply-To: <201409271919.s8RJJwPx019024@skeeve.com>

On Sat, Sep 27, 2014 at 10:19:58PM +0300, Aharon Robbins wrote:
> This is really gonna stretch the memories. (I may have even asked about
> it on this list before.)
> At one of the earlier USENIX conferences that I attended, maybe in
> Atlanta, there was a contest to make up humorous new errno values.

I'm back from a trip to Cania Gorge in Queensland Australia where there is
next to no phone reception.

When I scanned in the old AUUG newsletters, I told the photocopier to also
do OCR. This means that I can do this to the scanned files:

for i in *.pdf
do j=`echo $i | sed 's/pdf/txt/'`
   echo $j
   pdftotext $i
   grep ENO $j
   rm $j
done

Yet another reason why Unix is so much better :-) Here are the results
which will help Arnold out with his question.

Cheers, Warren

http://minnie.tuhs.org/Archive/Documentation/AUUGN/

AUUGN-V07.23.txt
ENOTOBACCO
ENOHORSE
ENONSEQUITUR

AUUGN-V07.45.txt
ENOINSTRUCTIONSET
ENOSTD
ENOP
ENOTON UNIX
ENOVAX
ENOFOOT
ENOCOFFEE
ENOLICENCE
ENOLICENSE
ENOTUNIX
ENOMONEYNOFUN
ENOTFOUND
ENOALCHOHOL
ENOJOY
ENOBAR
ENOTOBACCO

AUUGN-V08.34.txt
ENOTABACCO, read on an empty pipe?
ENOGOOD
ENOWARP
ENOTHEAVY
ENOUGH
ENOTONHORSE
ENOPHONEBOOK
ENOCONTEST
ENOARMSCONTROL
ENOSTRADAMUS
ENOAIR
ENOARMSCONTROL
ENOBOZOS
ENOCH
ENOCHICKEN
ENOCONTEST
ENOCORN
ENOCURRENT
ENODICE
ENOENO
ENOENO
ENOERROR
ENOFLUID
ENOGOOD
ENOGREYHOUND
ENOH20
ENOHOPE
ENOKISS
ENOKNOW
ENOMAAM
ENOMULTIHOP
ENON
ENONCOGNISCENT
ENONO
ENOONE
ENOPAPER
ENOPHONEBOOK
ENORMOUS
ENOSALT
ENOSAUSAGE
ENOSELECTRIC
ENOSTRADAMUS
ENOTATE
ENOTCOMPLETE
ENOTHEAVY
ENOTME
ENOTMYFAULT
ENOTONHORSE
ENOUGH
ENOUGH
ENOUGH
ENOUGH
ENOUNIX
ENOV1CE
ENOWARP
ENOWA.Y

AUUGN-V09.6.txt
ENOTUNIX
ENOTOBACCO





  parent reply	other threads:[~2014-10-02 11:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27 19:19 Aharon Robbins
2014-09-27 20:25 ` Dave Horsfall
2014-09-27 20:58   ` Warren Toomey
2014-09-27 21:16     ` Dave Horsfall
2014-09-28 10:01   ` Dave Horsfall
2014-09-28 15:04     ` Ronald Natalie
2014-09-28 16:22       ` Jaap Akkerhuis
2014-09-27 20:41 ` Jaap Akkerhuis
2014-09-27 21:09 ` Clem Cole
2014-09-28  4:44   ` arnold
2014-09-28  4:54     ` Larry McVoy
2014-09-28 14:06 ` John Cowan
2014-10-02 11:46 ` Warren Toomey [this message]
2014-10-02 12:12   ` arnold
2014-10-02 22:19     ` Warren Toomey
2014-10-03  9:24       ` arnold
2014-10-02 14:52   ` Derrik Walker v2.0
2014-10-02 13:00 Norman Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141002114626.GA548@www.oztivo.net \
    --to=wkt@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).