From: Ron Natalie <firstname.lastname@example.org>
Subject: [TUHS] Re: Unix V8 Chaosnet, any takers?
Date: Sun, 17 Jul 2022 21:01:21 -0400 [thread overview]
Message-ID: <989584CD-08CF-465B-88D1-8C0711B50D11@ronnatalie.com> (raw)
We had NCP running on the JHU kernel which essentially a V6 kernel with extra stuff (including the ability to mount both V6 and V7 disks). This was done on an 11/34 at Xmas time 1982 when the Arpanet went to long leaders and the UofIll ANTS we had became obsolete.
> On Jul 17, 2022, at 19:40, email@example.com wrote:
>> From: Warner Losh
>>> What's "net unix" anyway?
>> I'm referring to the University of Illinois distribution
> Ah, OK.
>> I have seen references to it in the ARPAnet census documents running on
>> both V6 and V7 (though mostly they were silent about which version).
> Well, V7 came out in January, 1979, and NCP wasn't turned off until January,
> 1983, so people had a lot of time to get it running under V7.
>> I thought this was the normal nomenclature of the time, but I may be
> I'm not sure what it was usually called; we didn't have much contact with it
> at MIT (although I had the source; I'm the one that provided it to TUHS).
> The problem was that although MIT had two IMPs, all the ports on them were
> spoken for, for big time-sharing mainframes (4 PDP-10's running ITS; 1
> running TWENEX; a Multics), so there were no ports available to plug in a
> lowly PDP-11. (We were unable to get an IP gateway (router) onto the ARPANET
> until MIT got some of the first C/30 IMPs.) So we had no use for the NCP Unix
> (which I vaguely recall was described as 'the ARPANET Unix from UIll').
next prev parent reply other threads:[~2022-07-18 1:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 23:39 Noel Chiappa
2022-07-18 1:01 ` Ron Natalie [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-18 17:07 Noel Chiappa
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).