The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Article on the history of cat(1)
Date: Wed, 14 Nov 2018 13:51:18 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.1811141338430.60610@aneurin.horsfall.org> (raw)
In-Reply-To: <20181114004018.GA23816@minnie.tuhs.org>

On Wed, 14 Nov 2018, Warren Toomey wrote:

>> Hell, I wish I still had that "CSU Tape"; it was Edition 6 with as much 
>> of Edition 7 (and AUSAM) that I could shoe-horn in, such as XON/XOFF 
>> for the TTY driver.  I was known as "Mr Unix 6-1/2" at the time...
>
> Definitely look at the UNSW tapes I have:
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=AUSAM
> and https://www.tuhs.org/Archive/Distributions/UNSW/
> in case any of these are what you are looking for.

I think I did before, but I confess I didn't spend much time on it.  My 
pride and joy was certainly the rewritten ei.c driver (implementing the 
200-UT batch protocol), and the clever workaround to an egregious KRONOS 
bug where it would get stuck in a POLL/REJECT loop (I merely sent a dummy 
command viz "Q,I" -- discarding the response -- because KRONOS was 
expecting a command instead of the correct REJECT being nothing to send 
from the batch emulator).

At the time, Unix got blamed because the smaller non-Unix /40s (running a 
standalone program) worked fine for some reason; my guess is that it 
implemented the broken protocol somehow.

-- Dave

  parent reply	other threads:[~2018-11-14  2:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 21:55 Warren Toomey
2018-11-13 22:44 ` Dave Horsfall
2018-11-13 22:49   ` Warren Toomey
2018-11-13 23:10     ` Arthur Krewat
2018-11-13 23:14     ` Dave Horsfall
2018-11-13 23:21       ` Rob Pike
     [not found]       ` <20181114004018.GA23816@minnie.tuhs.org>
2018-11-14  2:51         ` Dave Horsfall [this message]
2018-11-13 23:27 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=alpine.BSF.2.21.9999.1811141338430.60610@aneurin.horsfall.org \
    --to=dave@horsfall.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).