The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tuhs@cuzuco.com (Brian S Walden)
Subject: [TUHS] SYSV & TCP/IP on the VAX...
Date: Wed, 27 May 2009 13:39:19 -0400 (EDT)	[thread overview]
Message-ID: <200905271739.n4RHdJOf019727@cuzuco.com> (raw)

I seem to remember that for System V TCP/IP that you needed
STREAMS first, so that was SVR3. It may have been back potred
but I don't know. And after that, then you had a choice of
Wollongong or Lachman implementations. Bell Labs had their own as well,
but I believe that was only available internally. Amdahl UTS used
Lachman (which I kind of remember might have been Convergent's code),
but at Indian Hill it was removed and the home grown one put in.
I don't know who did the kernel code, but the user land utilities
were BSD ports done by Ralph Knag in Murray Hill. This was an
interesting setup as it was System/370 hardware so it had a 
channel to ethernet device from Spartacus, probably a K200 since
there was a "k200" command to fiddle with it. I largely ignored
TCP/IP initially as on the first UTS release, just telneting out of it
used a ton of system CPU, something would loop in the kernel instead of
going to sleep. Besides we had Datakit for interactive connectivity,
and NSC HyperChannel for intra-datacenter file transfer
(which I remember being something like 50mbs in 1987)

For the original SVR4, the official porting base was the 3b2 and that
group from Summit (which was later spun off as Unix Systems Laboraties
(USL)) used Lachman as well for it's TCP/IP.

> I was wondering if anyone had access to any SYSV for the VAX and could
> say what levels support TCP/IP?
> 
> I put in a request at http://www.novell.com/licensing/ntap/legal.html
> to see if they are even entertaining the sale of SYSV licenses... But
> I kind of figure they don't have the actual material itself....
> 
> I know A/UX a SYSVr2.2 had TCP/IP but I don't know if it was in the
> AT&T base, or if it was something that UniSoft had added...
> 
> Anyways thanks for any/all responses....
> 
> Oh and FWIW I've gotten a super minimal SYSIII thing booting on SIMH!
> I've just have to work out some more disk formatting/restoring as the
> root partition sizes don't agree between 32v & SYSIII....
> 
> Jason



             reply	other threads:[~2009-05-27 17:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 17:39 Brian S Walden [this message]
2009-05-27 18:20 ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2009-05-26 23:45 Jason Stevens
2009-05-26 23:48 ` Larry McVoy
2009-05-26 23:57   ` Jason Stevens
2009-05-26 23:59     ` Larry McVoy
2009-05-27  0:10       ` Jason Stevens
2009-05-27  3:06         ` John Cowan
2009-05-27  3:35           ` Jason Stevens
2009-05-27  4:05             ` M. Warner Losh
2009-05-27  0:32       ` Lyndon Nerenberg
2009-05-27  1:06       ` Corey Lindsly
2009-05-27  4:36         ` Gregg C Levine
2009-05-27  0:25   ` Lyndon Nerenberg

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=200905271739.n4RHdJOf019727@cuzuco.com \
    --to=tuhs@cuzuco.com \
    /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).