The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
	Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [TUHS] OSI stack (Was: Posters)
Date: Wed, 6 Feb 2019 17:04:06 -0700	[thread overview]
Message-ID: <CAK7dMtC3D3EZpUHnHii898miMxLtrO=ZTM0R=K_nkGqejsOzEg@mail.gmail.com> (raw)
In-Reply-To: <20190206235257.GU20698@mcvoy.com>

On Wed, Feb 6, 2019 at 4:52 PM Larry McVoy <lm@mcvoy.com> wrote:
>
> On Wed, Feb 06, 2019 at 04:40:24PM -0700, Kevin Bowling wrote:
> > Seems like a case of winners write the history books.  There were
> > corporate and public access networks long before TCP was set in stone
> > as a dominant protocol.  Most F500 were interchanging on SNA into the
> > 1990s.  And access networks like Tymnet, etc to talk to others.
>
> Yeah, but those were all tied to some vendor.  TCP/IP was the first
> wide spread networking stack that you could get from a pile of different
> vendors, Sun, Dec, SGI, IBM's AIX, every kernel supported it.   System V
> was late to the party, Lachman bought the rights to Convergent's STREAMs
> based TCP/IP stack and had a tidy business for a while selling that stack
> to lots of places.  It was an awful stack, I know because I ported it to
> a super computer and then to SCO's UNIX.  When Sun switched to a System
> Vr4 kernel, they bought it in some crazy bad deal and tried to use it
> in Solaris.  That lead to the tcp latency benchmark in lmbench because
> Oracle's clustered database ran like shit on Slowaris and I traced it
> down to their distributed lock manager and then whittled that code
> down to lat_tcp.c.  Sun eventually dumped that stack and went with
> Mentat's code and tuned that back up.  Sun actually dumped the socket
> code and went just with STREAMs interfaces but was forced to bring
> back sockets.  Socket's aren't great but they won and there is no
> turning back.
>
> > TCP, coupled with the rise of UNIX and the free wheel sharing of BSD
> > code, are what made the people to talk to.
>
> BSD wasn't free until much later than TCP/IP.  TCP/IP was developed in
> the 1970's.
>
> http://www.securenet.net/members/shartley/history/tcp_ip.htm
>
> https://www.livinginternet.com/i/ii_tcpip.htm

This is where I am out of my depth, was it a "success" before the
mid-late '80s as some dominant force?  My reading is no outside
universities with UNIX/BSD.  The meteoric success came a bit later in
the '80s with NSFNET, the rise of Cisco, and then the internet
exchange culture in the early '90s CIX, PAIX, Metropolitan Fiber
Systems etc got us to today and off Bell System stuff.

  reply	other threads:[~2019-02-07  0:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 23:18 Noel Chiappa
2019-02-06 23:40 ` Kevin Bowling
2019-02-06 23:52   ` Larry McVoy
2019-02-07  0:04     ` Kevin Bowling [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-07 19:04 Noel Chiappa
2019-02-07  1:03 Noel Chiappa
2019-02-07  0:45 Noel Chiappa
2019-02-07  0:02 Noel Chiappa
2019-02-07  0:11 ` Kevin Bowling
2019-02-06 17:49 Noel Chiappa
2019-02-06 18:22 ` Paul Winalski
2019-02-06 20:47 ` Kevin Bowling
2019-02-07 18:07   ` Grant Taylor via TUHS
2019-02-07 18:22     ` Andy Kosela
2019-02-07 18:50     ` Larry McVoy
2019-02-04 20:29 Noel Chiappa
2019-02-04 21:13 ` Bakul Shah
2019-02-04 21:34   ` Clem Cole
2019-02-05 18:01 ` Grant Taylor via TUHS
2019-02-03 18:49 Norman Wilson
2019-02-03 15:02 Noel Chiappa
2019-02-03 16:51 ` Grant Taylor via TUHS
     [not found] ` <CANCZdfq5PM9jFEi9=geC+CTnveXs5CprN7b+ku+s+FYzw1yQBw@mail.gmail.com>
2019-02-06 17:16   ` Warner Losh
2019-02-06 17:23     ` Larry McVoy
2019-02-06 23:37     ` George Michaelson

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='CAK7dMtC3D3EZpUHnHii898miMxLtrO=ZTM0R=K_nkGqejsOzEg@mail.gmail.com' \
    --to=kevin.bowling@kev009.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=lm@mcvoy.com \
    --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).