From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] 2.9bsd with networking on 18-bit possible?
Date: Tue, 11 Dec 2018 13:43:15 -0500 (EST) [thread overview]
Message-ID: <20181211184316.014E618C089@mercury.lcs.mit.edu> (raw)
> From: Clem Cole
> I could be mis remembering
No... :-)
> IIRC the original PTY driver goes back to the Rand and/or UofI for the
> NCP.
Yup. I found a pty.c in the NCP system, it's clearly the ancestor (comments
match):
https://minnie.tuhs.org//cgi-bin/utree.pl?file=SRI-NOSC/dmr/pty.c
> I suspect BBN got it from the Bruce Borden's Rand distribution tape
Or possibly indirectly; my copy of the NCP came from NOSC via SRI. In addition
to the one above, there are also these:
https://minnie.tuhs.org//cgi-bin/utree.pl?file=SRI-NOSC/dmr/misc/pty.c.ill
https://minnie.tuhs.org//cgi-bin/utree.pl?file=SRI-NOSC/dmr/misc/pty.c.x
Here:
https://minnie.tuhs.org//cgi-bin/utree.pl?file=BBN-V6/dmr/pty.c
is the BBN version, you can compare the them all. The MIT one is derived from
the BBN one.
> Named Piped were definiately a Rand-ism (they were originally called 'Rand Pipes')
Well, _RAND_ called them 'ports':
https://minnie.tuhs.org//cgi-bin/utree.pl?file=BBN-V6/doc/ipc/ports
> But there were issues and somethings were not 100% until the UofI NCP;
> which was the first really complete NCP for UNIX.
Somewhere I found a document about the UofI code, I think they wrote it from
scratch? Sorry, too lazy to look at it. See here:
https://minnie.tuhs.org//cgi-bin/utree.pl?file=SRI-NOSC
for links.
Noel
next reply other threads:[~2018-12-11 18:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 18:43 Noel Chiappa [this message]
2018-12-11 18:51 ` Clem Cole
2018-12-12 1:20 ` Jacob Ritorto
-- 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 16:57 Noel Chiappa
2018-12-11 17:01 ` Jon Forrest
2018-12-11 18:03 ` Clem Cole
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=20181211184316.014E618C089@mercury.lcs.mit.edu \
--to=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).