Computer Old Farts Forum
 help / color / mirror / Atom feed
From: grog at lemis.com (Greg 'groggy' Lehey)
Subject: [COFF] Confused managers (was finger usage (was: pronouncing *nix formulas (was: screen editors)))
Date: Sat, 8 Feb 2020 10:15:07 +1100	[thread overview]
Message-ID: <20200207231507.GA75158@eureka.lemis.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2002080933200.33501@aneurin.horsfall.org>

On Saturday,  8 February 2020 at  9:37:22 +1100, Dave Horsfall wrote:
> On Fri, 7 Feb 2020, Greg 'groggy' Lehey wrote:
>
>> But over the years I've been surprised how many people have been fooled.
>
> I'm sure that we've all pulled pranks like that.  My favourite was piping
> the output of "man" (a shell script on that system) through "Valley Girl"
> (where each "!" was followed e.g. by "Gag me with a spoon!" etc).
>
> Well, $BOSS came into the office after a "heavy" night, and did something
> like "man uucp", not quite figuring out what was wrong; I was summoned
> shortly afterwards, as I was the only possible culprit...

That brings back another recollection, not Unix-related.

In about 1978 I was getting fed up with the lack of clear text error
messages from Tandem's Guardian operating system.  A typical message
might be

  FILE SYSTEM ERROR 011

Yes, Tandem didn't use leading 0 to indicate octal.  This basically
meant ENOENT, but it was all that the end user saw.  By chance I had
been hacking in the binaries and found ways to catch such messages and
put them through a function which converted them into clear text
messages.  For reasons that no longer make sense to me, I stored the
texts in an external file, which required a program to update it.

Early one morning I was playing around with this, and for the fun of
it I changed the text for error 11 from "File not found" to "Please
enter FUP PURGE ! *" (effectively rm -f *).

I was still giggling about this when the project manager came to me
and said "Mr. Lehey, I think I've done something silly".

Thank God for backups!  We were in a big IBM shop, and the operators
religiously ran a backup every night.  Nothing lost.

Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200208/d9fa5ae7/attachment.sig>


           reply	other threads:[~2020-02-07 23:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <alpine.BSF.2.21.9999.2002080933200.33501@aneurin.horsfall.org>]

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=20200207231507.GA75158@eureka.lemis.com \
    --to=coff@minnie.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).