The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix V8 Chaosnet, any takers?
Date: Sat, 16 Jul 2022 11:02:06 -0600	[thread overview]
Message-ID: <CANCZdfryFqyDYLMag4EZ5uNMWsTTvmcK1yeb5qoO2V3pJ88C+A@mail.gmail.com> (raw)
In-Reply-To: <20220716155121.4873618C087@mercury.lcs.mit.edu>

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

On Sat, Jul 16, 2022 at 9:51 AM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:

>     > From: Warner Losh
>
>     > V7 could mean a modification of net unix
>
> What's "net unix" anyway? I know of the Net releases from CSRG, but this
> much precedes that.
>

I'm referring to the University of Illinois distribution that's in TUHS as
Distributions/Early_Networking/NOSC.
Steve Holmgren led the effort, and it was quite popular. It was V6 based
(it came out in late V5 time frame,
just before V6 was released and quickly updated, the version we have
appears to be based on a pure V6
release). 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). It was NCP, not TCP/IP. I
thought this was the normal nomenclature
of the time, but I may be mistaken.


> What did people with PDP-11 V7 who wanted TCP/IP do, anyway?
>

We also have BBN's stack as well in Distributions/Early_Networking/BBN. It
appears to be for an 11/40, 11/45
or 11/70, though that's based purely on different files having '70', '45'
and '40' in their name. These are also based
on V6 (at least the code we have has a V6 layout and the few files I diff'd
to V6 were pretty close). There's also an
early VAX version in that directory as well.

One could adapt either of these to V7, and I seem to recall seeing
references to people that did that in the stuff
I read for some of my early Unix talks, but I can't seem to find it right
now.

Warner

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

  reply	other threads:[~2022-07-16 17:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 15:51 Noel Chiappa
2022-07-16 17:02 ` Warner Losh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-18 17:07 Noel Chiappa
2022-07-17 23:39 Noel Chiappa
2022-07-18  1:01 ` Ron Natalie
2022-07-16 20:02 Paul Ruizendaal
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=CANCZdfryFqyDYLMag4EZ5uNMWsTTvmcK1yeb5qoO2V3pJ88C+A@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=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).