The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Andrew Hume <andrew@humeweb.com>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] EGREG
Date: Sun, 17 Jan 2021 21:39:04 -0800	[thread overview]
Message-ID: <135414D4-7982-4015-BEE7-39EBFC930B36@humeweb.com> (raw)
In-Reply-To: <20210117205243.739CB43F88@lignose.oclsc.org>

the evidence looks damning, but i still can’t recall.

i will, however, admit to this driver incorporating some code
my cat typed. i had left my (sam) editor open on the driver
and the cat trampled on the keyboard. unfortunately, it was centered
on a octal constant (setting some bits in a control register) and so went
undetected for a few days. darn kitty!

andrew

> On Jan 17, 2021, at 12:52 PM, Norman Wilson <norman@oclsc.org> wrote:
> 
> 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;
> 	}
> 
> 
> Norman Wilson
> Toronto ON


  parent reply	other threads:[~2021-01-18  6:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-17 20:52 Norman Wilson
2021-01-17 21:14 ` Larry McVoy
2021-01-17 23:20   ` Rob Pike
2021-01-18  5:39 ` Andrew Hume [this message]
  -- 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=135414D4-7982-4015-BEE7-39EBFC930B36@humeweb.com \
    --to=andrew@humeweb.com \
    --cc=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).