From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Names of famous, historical UNIX machines?
Date: Fri, 3 Feb 2017 12:59:04 +0000 [thread overview]
Message-ID: <C78C3CAB-11DD-4018-9CC4-410766370C51@tfeb.org> (raw)
In-Reply-To: <28ebecfb41ed0b72b45f1cd2ae99c3a4@xs4all.nl>
I am not sure if I remember this or if I was told it later, but mcvax was a very important machine for people in Europe (like me) as it was a big gateway (for usenet? I forget). Its name was in lots of people's heads and probably lots of scripts &c. So at some point they got a new machine which, obviously, was a Sun. So, at that point they had two choices:
- keep the old name, even though it wasn't a VAX any more;
- rename it to something which was platform-neutral so the pain would only happen once.
And they took the third option: rename it, but wire-in the platform *again* thus causing pain now and more pain later. Oh dear.
On the subject of hostnames, has anyone mentioned prep / prep.ai.mit.edu? All the GNU software came from that in the mid 1980s, anyway. I think 'prep' meant 'document preparation', I don't know what it was.
--tim
> On 1 Feb 2017, at 22:54, Jacob Goense <dugo at xs4all.nl> wrote:
>
> - mcvax, mcsun
> Suitable for anything related to europe.
next prev parent reply other threads:[~2017-02-03 12:59 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
2017-02-03 12:59 ` Tim Bradshaw [this message]
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=C78C3CAB-11DD-4018-9CC4-410766370C51@tfeb.org \
--to=tfb@tfeb.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).