The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] Names of famous, historical UNIX machines?
Date: Wed, 1 Feb 2017 20:43:27 +0000	[thread overview]
Message-ID: <20170201204327.GU21797@yeono.kjorling.se> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]

I hope this isn't too far off topic here.

I've been meaning to rename the few systems I administer with names
that reference famous (or at least somewhat well-known in the proper
circles) historical UNIX systems, but I have been unable to find any
lists of such names so have no real place to start. About the closest
I _was_ able to find is the ARPANET map[1] of the late 1970s that is
on Wikipedia and is occasionally circulated, but which gives mostly
architecture, location and links, not any system (host) names.

Short of unimaginative things like calling my home router IMP[2] or
things like that, can anyone either suggest names with a bit of
background (where they were, what hardware, what time period, etc.),
or point me toward online resources where I can find lists of those?


 [1]: https://en.wikipedia.org/wiki/File:Arpanet_logical_map,_march_1977.png

 [2]: https://en.wikipedia.org/wiki/Interface_Message_Processor

-- 
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
                 “People who think they know everything really annoy
                 those of us who know we don’t.” (Bjarne Stroustrup)


             reply	other threads:[~2017-02-01 20:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 20:43 Michael Kjörling [this message]
2017-02-01 20:46 ` Clem Cole
2017-02-01 20:50 ` Clem Cole
2017-02-01 21:11   ` Lars Brinkhoff
2017-02-01 21:20   ` Noel Chiappa
2017-02-01 21:42     ` Michael Kjörling
2017-02-01 21:43       ` Cory Smelosky
2017-02-01 22:16         ` Cory Smelosky
2017-02-01 21:50       ` William Pechter
2017-02-01 22:06     ` Clem Cole
2017-02-01 22:11       ` Larry McVoy
2017-02-01 22:21         ` Clem Cole
2017-02-01 22:28         ` Clem Cole
2017-02-01 22:44           ` William Pechter
2017-02-02  1:14             ` Rico Pajarola
2017-02-02  1:34               ` Clem Cole
2017-02-02  1:18             ` Clem Cole
2017-02-02  1:29               ` Clem Cole
2017-02-02 13:11           ` arnold
2017-02-04  3:46             ` Steve Johnson
2017-02-04  3:56               ` Larry McVoy
2017-02-04 22:48                 ` Nemo
2017-02-01 22:26     ` Arthur Krewat
2017-02-02  7:38       ` Lars Brinkhoff
2017-02-01 21:33 ` Larry McVoy
2017-02-01 21:57   ` Clem Cole
2017-02-01 22:08     ` Larry McVoy
2017-02-01 22:20       ` Steve Nickolas
2017-02-03  1:51   ` Dave Horsfall
2017-02-01 22:54 ` Jacob Goense
2017-02-03 12:59   ` Tim Bradshaw
2017-02-03 14:04   ` Dave Horsfall
2017-02-03 14:11     ` Jacob Goense
2017-02-03 15:12       ` Arthur Krewat
2017-02-06  5:41       ` Dave Horsfall
2017-02-03  5:50 ` Lars Brinkhoff
2017-02-01 22:16 Noel Chiappa
2017-02-01 22:27 Berny Goodheart
2017-02-02  9:59 Rudi Blom

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=20170201204327.GU21797@yeono.kjorling.se \
    --to=michael@kjorling.se \
    /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).