The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Norman Wilson <norman@oclsc.org>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Old mainframe I/O speed (was: core)
Date: Sun, 24 Jun 2018 14:49:46 -0400	[thread overview]
Message-ID: <1529866190.27006.for-standards-violators@oclsc.org> (raw)

Paul Winalski:

  That was the VAXstation-11/RC.

===

Yep, that's the name.

My first batch of discarded MicroVAX IIs were the original
backbone routers for a large university campus, installed
ca. 1990.  That backbone ran over serial-line connections,
at 56Kbps, which was quite impressive for the day given the
physical distances involved.

Either they had a bunch of Qbus backplanes lying around, or
someone computed that the cost of an 11/RC plus a backplane
was appreciably less than a system with an unobstructed
backplane.  In any case, they swapped most of the backplanes
themselves.  The one I got that still had the glue in was an
anomaly; maybe it was a spare chassis.

The MicroVAX routers ran Ultrix, and some of them had uptimes
of five years when they were finally shut down to be discarded.
All the hardware I rescued tested out fine, and some of it is
still running happily in my basement.  I've had a few disk
failures over the years, and I think lost one power supply
back around Y2K and maybe had a DZV11 fail, but that's it.
We don't make hardware like that any more.

Norman Wilson
Toronto ON

             reply	other threads:[~2018-06-24 18:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-24 18:49 Norman Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-24 18:49 Norman Wilson
2018-06-24  3:14 Norman Wilson
2018-06-24 13:03 ` Paul Winalski
2018-06-24 14:41   ` Lawrence Stewart
2018-06-24 15:47     ` Arthur Krewat
     [not found] <mailman.1.1529690481.3725.tuhs@minnie.tuhs.org>
2018-06-23 10:32 ` Johnny Billquist
2018-06-23 11:39   ` Clem cole
2018-06-24  7:50   ` Mutiny
2018-06-27 13:59     ` Clem Cole
2018-06-22 13:11 Noel Chiappa
2018-06-22 17:49 ` Erik E. Fair
2018-06-15 15:25 [TUHS] core Noel Chiappa
2018-06-15 23:05 ` Dave Horsfall
2018-06-15 23:22   ` Lyndon Nerenberg
2018-06-16  6:36     ` Dave Horsfall
2018-06-16 19:07       ` Clem Cole
2018-06-18  9:25         ` Tim Bradshaw
2018-06-19 20:45           ` Peter Jeremy
2018-06-19 22:55             ` David Arnold
2018-06-20  5:04               ` Peter Jeremy
2018-06-20  5:41                 ` Warner Losh
2018-06-20  8:10                   ` [TUHS] Old mainframe I/O speed (was: core) Greg 'groggy' Lehey
2018-06-20 16:33                     ` Paul Winalski
2018-06-21  3:05                       ` Peter Jeremy
2018-06-21 14:00                         ` Paul Winalski
2018-06-21 14:49                           ` Arrigo Triulzi
2018-06-21 20:39                             ` Paul Winalski
2018-06-22  5:32                               ` Erik E. Fair
2018-06-22 13:32                                 ` Clem Cole
2018-06-23  6:08                             ` Dave Horsfall
2018-06-23 17:02                               ` ron minnich

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=1529866190.27006.for-standards-violators@oclsc.org \
    --to=norman@oclsc.org \
    --cc=tuhs@tuhs.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).