The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] OSI stack (Was: Posters)
Date: Wed,  6 Feb 2019 20:03:22 -0500 (EST)	[thread overview]
Message-ID: <20190207010322.DB0AA18C07B@mercury.lcs.mit.edu> (raw)

    > From: Kevin Bowling

    > t just doesn't mesh with what I understand

Ah, sorry, I misunderstood your point.

Anyway, this is getting a little far afield for TUHS, so at some point it
would be better to move to the 'internet-history' list if you want to explore
it in depth. But a few more...

    > Is it fair to say most of the non-gov systems were UNIX during the next
    > handful of years?

I assume you mean 'systems running TCP/IP'? If so, I really don't know,
because for a while during that approximate period one saw many internets
which weren't connected to the Internet. (Which is why the capitalization is
important, the ill-educated morons at the AP, etc notwithstanding.) I have no
good overall sense of that community, just anecdotal (plural is not 'data').

For the ones which _were_ connected to the Internet, then prior to the advent
of the DNS, inspection of the host table file(s) would give a census. After that,
I'm not sure - I seem to recall someone did some work on a census of Internet
machines, but I forget who/were.

If you meant 'systems in general' or 'systems with networking of some sort', alas
I have even less of an idea! :-)

	Noel

             reply	other threads:[~2019-02-07  1:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07  1:03 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-07 19:04 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 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=20190207010322.DB0AA18C07B@mercury.lcs.mit.edu \
    --to=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).