The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 2.9bsd with networking on 18-bit possible?
Date: Tue, 11 Dec 2018 13:03:27 -0500	[thread overview]
Message-ID: <CAC20D2MQWqAOXFe18n+NaEiwfv-w4adTMnRzzftEj3svf0dagg@mail.gmail.com> (raw)
In-Reply-To: <20181211165707.3A1E618C089@mercury.lcs.mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

On Tue, Dec 11, 2018 at 11:57 AM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:

>     > we must have added PTY's of some sort
>
> There is indeed a PTY driver; it has comments from BBN'ers who edited it,
> so
> perhaps we got it from BBN.
>

Hmm, I could be mis remembering, but IIRC the original PTY driver goes back
to the Rand and/or UofI for the NCP.  I suspect BBN got it from the Bruce
Borden's Rand distribution tape which was 74 or 75, I think.  Named Piped
were definiately a Rand-ism (they were originally called 'Rand Pipes') and
were on that tape along with their Editor.

It's too bad Greg is not here to ask.    My memory and Noel may know by the
IMP release dates, is that Rand was on connected before UofI.  But there
were issues and somethings were not 100% until the UofI NCP; which was the
first really complete NCP for UNIX.    I'm pretty sure that Greg's version
went back to Bruce, as well as to BBN and Harvard and I would have assumes
MIT also.

I don't remember if the original Rand Pipes and PTYs were 5th or 6th
edition originally.   I'm fairly sure, UofI's NCP was 6th edition but think
that Rand goes back to at least 5th if not 4th.
ᐧ

[-- Attachment #2: Type: text/html, Size: 2591 bytes --]

  parent reply	other threads:[~2018-12-11 18:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 16:57 Noel Chiappa
2018-12-11 17:01 ` Jon Forrest
2018-12-11 18:03 ` Clem Cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-15  1:54 Paul Ruizendaal
2018-12-12 17:55 Paul Ruizendaal
2018-12-12 14:38 Noel Chiappa
2018-12-12 14:14 Noel Chiappa
2018-12-12 10:29 Paul Ruizendaal
2018-12-11 18:43 Noel Chiappa
2018-12-11 18:51 ` Clem Cole
2018-12-12  1:20   ` Jacob Ritorto
2018-12-11 16:16 Noel Chiappa
2018-12-11 16:26 ` Clem Cole
2018-12-11  4:42 Noel Chiappa
2018-12-11  2:11 Noel Chiappa
2018-12-11  2:36 ` Grant Taylor via TUHS
2018-12-11  3:28   ` Warner Losh
2018-12-10 22:05 Jacob Ritorto
2018-12-11  1:21 ` Clem cole
2018-12-11  1:55   ` Grant Taylor via TUHS
2018-12-11  7:22     ` Lars Brinkhoff
2018-12-11 15:28       ` Clem Cole
2018-12-11 17:21         ` Lars Brinkhoff

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=CAC20D2MQWqAOXFe18n+NaEiwfv-w4adTMnRzzftEj3svf0dagg@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@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).