From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Names of famous, historical UNIX machines?
Date: Wed, 1 Feb 2017 13:33:31 -0800 [thread overview]
Message-ID: <20170201213331.GD880@mcvoy.com> (raw)
In-Reply-To: <20170201204327.GU21797@yeono.kjorling.se>
Oh, I've got some. Not that old, 80's.
UW-Madison
slovax - 11/750 that had the BSD sources on it. Spent many a happy
hour reading there and I've always had a personal machine
called slovax ever since. mcvoy.com internally is slovax.
speedy - 8600 that was the main research/faculty machine. Also
...!uwisc!rsch
Tokoyo Institute of Technology (TIT)
So the back story here is I was one of the Unix geeks doing a Unix
port to the ETA-10. TIT was taking delivery of a big liquid cooled
machine and of course we weren't ready. I got sent over with 3 tapes,
one was the baseline that was sort of checked in, one was my port of
Lachman (who bought it from I think Convergent)'s TCP/IP stack, and
one was some VM thing, I think big pages but I'm not sure.
They sent me over there with a small replica of our development
environment (Sun 3/260 file / compute server and 2 3/50 workstations)
and told me "Merge this stuff and install it, TIT wants all of it".
So I get to Tokoyo and the machines show up and I'm installing SunOS
and I have to name them:
3/260: BigTIT
3/50: LeftTIT
3/50: RightTIT
and I even put them physically how you would imagine.
It only lasted until they figured out what it meant but I didn't get
in trouble. Because a different story had just happened that had
made the Japanese sales guys bust up in laughter and they had taken
me out we all got shit faced a few days before I had to rename the
machines. Happy to share that story if anyone is still reading :)
Sun
The source machines that held the SCCS history before they went to
NSE/NSElite/Teamware:
Argon
Radon
Krypton
That's all I can think of for now, not sure if any of it is actually that
all interesting.
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2017-02-01 21:33 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 [this message]
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=20170201213331.GD880@mcvoy.com \
--to=lm@mcvoy.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).