The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: [TUHS] EGREG
Date: Sun, 17 Jan 2021 15:52:43 -0500 (EST)	[thread overview]
Message-ID: <20210117205243.739CB43F88@lignose.oclsc.org> (raw)

Andrew Hume (dammit andrew):

  i have probed recently about the origins of the b\x1cEGREGb\x1d (its all greg cession's fault) error in Research Unix.
  alas, i recall nothing about this, and can't recall ever getting the message.

===

Your memory fails you, which is not unreasonable for stuff you
probably haven't thought about in more than 30 years:

/*
	SCSI Pass-Thru driver for the TD Systems UD? -- Andrew Hume
	Ninth Edition Unix
*/

[...]

scsiwrite(dev)
	dev_t dev;
{
	register count;
	register struct scsi *p = &scsi[minor(dev)];
	register struct mscmd *cmd = &p->junk->cmd.msg;
	unsigned char flag, bus_id;

	if(p->flag&NEXTWR)
		p->flag &= ~NEXTWR;
	else {
		u.u_error = EGREG;
		return;
	}

As I remember it, EGREG went into errno.h and libc out
of a desire to have some never-normally-used error to
be returned when debugging.  I forget just who was in
the UNIX Room conversation that created it; almost certainly
I was.  I thought andrew was as well; very likely one or
more of andrew td presotto.

I do remember being a bit annoyed at Andrew for putting it
in permanent use in the raw-SCSI driver (which was at the
time of interest mainly to Andrew for controlling an
early optical-disc jukebox, used by the original File
Motel backup system).

As to the origin of `It's all Greg's fault' as a meme,
that was already around and established when I arrived at
the Labs in mid-1984, though Greg himself had already
moved west.  Maybe Doug or Ken remembers how that started.

Andrew himself was responsible for or blamed by more than
one meme of the days.  The scsi driver spawned one, in fact:
the first attempt used a SCSI interface from Emulex, which
never worked quite right, and despite repeated phone calls
to Emulex Andrew could never get it figured out.  He tried
and tried, though, and his attempts spawned the catch
phrase `Time to call Emulex again!'

Norman Wilson
Toronto ON

             reply	other threads:[~2021-01-17 20:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-17 20:52 Norman Wilson [this message]
2021-01-17 21:14 ` Larry McVoy
2021-01-17 23:20   ` Rob Pike
2021-01-18  5:39 ` Andrew Hume
  -- strict thread matches above, loose matches on Subject: below --
2021-01-17 14:57 Andrew Hume
2021-01-17 16:37 ` ron minnich
2021-01-17 16:39   ` Andrew Hume

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=20210117205243.739CB43F88@lignose.oclsc.org \
    --to=norman@oclsc.org \
    --cc=tuhs@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).