From: dugo@xs4all.nl (Jacob Goense)
Subject: [TUHS] Names of famous, historical UNIX machines?
Date: Wed, 01 Feb 2017 17:54:38 -0500 [thread overview]
Message-ID: <28ebecfb41ed0b72b45f1cd2ae99c3a4@xs4all.nl> (raw)
In-Reply-To: <20170201204327.GU21797@yeono.kjorling.se>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
On 2017-02-01 15:43, Michael Kjörling wrote:
> 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?
I could drop names, but at some point the labels became quite uniform.
To illustrate that, look at the labels in an old top1000 of USENET
sites.
http://top1000.anthologeek.net/2000/12/full.txt
They bore quickly.
The largest secondary tld nameserver ever was simply called ns
(ns.EU.net),
I don't recall the internal hostname, but it was probably some norse
god like balder or buri.
Some stuff that randomply pops up in my mind:
- anon and penet
Reference to anon.penet.fi, early to mid '90s, a generic 386/486 box at
Julfs house and at undisclosed locations later on.
Suitable for naming mail relays, outgoing mail servers and anonymity
realetd services.
- kremvax
Fictional machine. Suitable for jokes, routers related to anything in
the east.
- mcvax, mcsun
Suitable for anything related to europe.
- sunsite
A 90s thing. Suitable for sharing software, and, as a pun on Sun, java
related stuff maybe.
- gatekeeper
Again, labels became boring, ftp.uu.net was famous as ftp site, but
gatekeeper.dec.com had
a cool hostname.
- chronos
chronos.eu.net was a go to time server in europe, replaced by
rolex.ripe.net.
- agate
After agate.berkeley.edu, where BSD escaped the university until the
lawyers stepped in.
next prev parent reply other threads:[~2017-02-01 22:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=28ebecfb41ed0b72b45f1cd2ae99c3a4@xs4all.nl \
--to=dugo@xs4all.nl \
/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).