From: berny@berwynlodge.com (Berny Goodheart)
Subject: [TUHS] Names of famous, historical UNIX machines?
Date: Wed, 1 Feb 2017 22:27:37 +0000 [thread overview]
Message-ID: <95DE698C-924C-4DA8-AD22-681A612D0421@berwynlodge.com> (raw)
You might find this interesting reading:
http://www.livinginternet.com/u/ui_netexplodes.htm <http://www.livinginternet.com/u/ui_netexplodes.htm>
In particular inhp4. I used to have a UUCP map that linked me into this network back in the mid 80s. I was based in the UK doing some work for Henry Spencer at Microport Systems if any of you recall their iX286 System V port, which was pretty cool.
Anyway, there are some interesting machine names mentioned.
From: smb@ulysses.att.com
Subject: Re: IHNP4
Date: Thu, 25 Oct 90 20:48:42 EDT
> Thus, ihnp4 was Indian Hill Network Processor #4
> mh was Murray Hill. ak was the Atlanta Wire Works, sb was Southern
> Bell, cb was Columbus (Mark Horton was mark at cbosgd for a long time)
> plus others.
Yup, Columbus Operating Systems Group D, as I recall.
> Then there were the machines in the lab that had (and have) names like
> bonnie, clyde, ulysses, research, allegra, lento, harpo, chico, etc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170201/46596fdc/attachment.html>
next reply other threads:[~2017-02-01 22:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 22:27 Berny Goodheart [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-02 9:59 Rudi Blom
2017-02-01 22:16 Noel Chiappa
2017-02-01 20:43 Michael Kjörling
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
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=95DE698C-924C-4DA8-AD22-681A612D0421@berwynlodge.com \
--to=berny@berwynlodge.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).