From: Kevin Bowling <kevin.bowling@kev009.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] OSI stack (Was: Posters)
Date: Wed, 6 Feb 2019 17:11:08 -0700 [thread overview]
Message-ID: <CAK7dMtBbQF00PP9ES2jWPBseg7pdBqJPsP-w8y32DugQE+Espg@mail.gmail.com> (raw)
In-Reply-To: <20190207000255.E1F1318C084@mercury.lcs.mit.edu>
On Wed, Feb 6, 2019 at 5:03 PM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>
> > From: Kevin Bowling
>
> > Seems like a case of winners write the history books.
>
> Hey, I'm just trying to pass on my best understanding as I saw it at the time,
> and in retrospect. If you're not interested, I'm happy to stop.
There's nothing personal. It just doesn't mesh with what I understand
from non-UNIX first party sources in some mainframe, telco, and
networking books. If I'm wrong I'll gladly update my opinion. I
wasn't there. I try to incorporate other sources outside UNIX into my
readings on computer history. Maybe I see connections where there
were none, or they really were just parallel universes that didn't
influence each other.
> > There were corporate and public access networks long before TCP was set
> > in stone as a dominant protocol.
>
> Sure, there were lots of alternatives (BITNET, HEPNET, SPAN, CSNET, along with
> commercial systems like TYMNET and TELENET, along with a host of others whose
> names now escape me). And that's just the US; Europe had an alphabet soup of its
> own.
>
> But _very_ early on (1 Jan 1983), DARPA made all their fundees (which included
> all the top CS departments across the US) convert to TCP/IP. (NCP was turned
> off on the ARPANET,and everyone was forced to switch over, or get off the
> network.) A couple of other things went for TCP/IP too (e.g. NSF's
> super-computer network). A Federal ad hoc inter-departmental committee called
> the FRICC moved others (e.g. NASA and DoE) in the direction of TCP/IP,
> too.
>
> That's what created the large user community that eventually drove all the
> others out of business. (Metcalfe's Law.)
Is it fair to say most of the non-gov systems were UNIX during the
next handful of years? I am asking for clarification, not a leading
question.
Regards,
Kevin
next prev parent reply other threads:[~2019-02-07 0:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 0:02 Noel Chiappa
2019-02-07 0:11 ` 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-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
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=CAK7dMtBbQF00PP9ES2jWPBseg7pdBqJPsP-w8y32DugQE+Espg@mail.gmail.com \
--to=kevin.bowling@kev009.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).