The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Names of famous, historical UNIX machines?
Date: Wed,  1 Feb 2017 17:16:00 -0500 (EST)	[thread overview]
Message-ID: <20170201221600.2AD3B18C0E5@mercury.lcs.mit.edu> (raw)

    > From: Clem Cole

    > my printers have often been named after chainsaws

Yeah, MIT (or was it Proteon, I forget - a long time ago :-) had that theme
going for a while for printers...

    > @ DEC we were pretty free to use what we wanted and some were themed,
    > most were boring.

Hah! I do have a cosmically great computer naming story from DEC, though.

So DECNet host names were limited to N characters (where N=8, or some
such). So one day they get this complaint from some DEC user in the UK:

"Grumble, grumble, grumble, N-character limit in DECNet host names, we want to
name our host 'Slartibartfast'."

So, this being before a certain radio play had hit the US from the UK, the
people at DEC were like:

"What's a 'Slartibartfast'???"

Instantly, the reply shot back (and perhaps some of you saw this coming):

"Boy, you guys are so unhip it's a wonder your pants down fall down!" :-) :-)

      Noel


             reply	other threads:[~2017-02-01 22:16 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 22:16 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-02  9:59 Rudi Blom
2017-02-01 22:27 Berny Goodheart
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=20170201221600.2AD3B18C0E5@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).