From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: Unix V8 Chaosnet, any takers?
Date: Mon, 18 Jul 2022 13:07:35 -0400 (EDT) [thread overview]
Message-ID: <20220718170735.1401D18C08E@mercury.lcs.mit.edu> (raw)
> From: Ron Natalie
> We had NCP running on the JHU kernel
Which NCP implementation was that, the one from UIUC, or something else? (I'm
curious about the one that someone here - I forget who - mentioned, where
IIRC they thought it was a new one, not the UIUC one. I'm a little boggled
that with so little use for one - there weren't many NCP sites - someone
would have gone to all the work to do another one. But it's possible...)
If you all used the UIUC one, what did you call it? I looked through the email
about releases from NOSC (who seemed to be the focal point for maintaining
it at one point):
https://minnie.tuhs.org/cgi-bin/utree.pl?file=SRI-NOSC/new/dist.log
but it doesn't give a name for it. The documentation:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=SRI-NOSC/doc/IllinoisNCP.nr
doesn't either (other than 'Illinois NCP').
It does seem that they were semi-using V7; see e.g.:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=SRI-NOSC/green/c.c
but the code looks very V6-ish; see e.g.:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=SRI-NOSC/ken/text.c
Noel
next reply other threads:[~2022-07-18 17:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 17:07 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-17 23:39 Noel Chiappa
2022-07-18 1:01 ` Ron Natalie
2022-07-16 20:02 Paul Ruizendaal
2022-07-16 15:51 Noel Chiappa
2022-07-16 17:02 ` Warner Losh
2022-07-15 10:25 Noel Chiappa
2022-07-15 11:53 ` Theodore Ts'o
2022-07-16 6:59 ` Lars Brinkhoff
2022-07-15 8:51 Paul Ruizendaal via TUHS
2022-07-14 11:08 [TUHS] " Lars Brinkhoff
2022-07-14 16:37 ` [TUHS] " John Floren
2022-07-14 17:00 ` Lars Brinkhoff
2022-07-14 17:51 ` segaloco via TUHS
2022-07-14 18:19 ` Ron Natalie
2022-07-14 20:32 ` Tom Teixeira
2022-07-14 20:39 ` Ron Natalie
2022-07-15 0:33 ` Grant Taylor via TUHS
2022-07-15 4:29 ` Erik E. Fair
2022-07-14 19:36 ` Lars Brinkhoff
2022-07-14 21:50 ` segaloco via TUHS
2022-07-16 6:38 ` Lars Brinkhoff
2022-07-16 14:05 ` Warner Losh
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=20220718170735.1401D18C08E@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).