The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Release of 8th, 9th and 10th Editions Unix
Date: Wed, 29 Mar 2017 21:17:34 -0600	[thread overview]
Message-ID: <CANCZdfpi7NKRzOhT=9xgxstmXJVdPpcpd-MHiAMmdO0PWR5DFw@mail.gmail.com> (raw)
In-Reply-To: <58db807d.qn8Xmvl3ZuN+bN3u%schily@schily.net>

On Wed, Mar 29, 2017 at 3:38 AM, Joerg Schilling <schily at schily.net> wrote:
> George Ross <gdmr at inf.ed.ac.uk> wrote:
>
>> > I think that the 3/50 was a "single board" VME system... and as you say
>> > you really couldn't add anything to it.
>>
>> IIRC the only way to add anything to it was to pull the processor from its
>> socket, plug in a daughterboard, and then plug the processor back into that.
>> It did feel a whole lot more responsive with that extra 8MB of memory!
>
> The method to "upgrade" a Sun-3/50 was to pull the gate arrays and add a
> doughter board. There have been such extensions from "Sunflower". A company
> that was latrer forced by Sun to rename into "Solflower".

I know people that did unnatural things to upgrade the Sun 3/50 to
something that had enough memory not to suck. Oh, and to have real
disks, rather than the crazy SCSI to ESDI disks that had performance
only marginally better than floppy drives....   IIRC, the hard part
was getting a VME "cage" to allow other cards to in inserted, which
killed the pizza-box implementation of the 3/50. But it's been a long
time since that happened, and maybe I'm misremembering. Maybe that was
only possible with the 3/60.

Warner


  reply	other threads:[~2017-03-30  3:17 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 20:24 Warren Toomey
2017-03-27 15:43 ` Cory Smelosky
2017-03-28  2:13   ` Larry McVoy
2017-03-28  2:14     ` Cory Smelosky
2017-03-28  8:03     ` Jason Stevens
2017-03-28  8:21       ` Cory Smelosky
2017-03-28 12:26     ` Brad Spencer
2017-03-28 14:38       ` Álvaro Jurado
2017-03-29  2:57       ` Greg 'groggy' Lehey
2017-03-28 15:23     ` Arthur Krewat
2017-03-28 15:27       ` Larry McVoy
2017-03-28 15:38         ` Dan Cross
2017-03-28 15:41           ` Larry McVoy
2017-03-28 17:30             ` Lyndon Nerenberg
2017-03-28 17:36               ` Larry McVoy
2017-03-28 15:46           ` Arthur Krewat
2017-03-28 16:18             ` ron minnich
2017-03-28 17:00             ` Brad Spencer
2017-03-28 17:42               ` Larry McVoy
2017-03-28 18:02                 ` Brad Spencer
2017-03-28 18:19                   ` Larry McVoy
2017-03-28 20:51                     ` Brad Spencer
2017-03-29  8:22                   ` George Ross
2017-03-29  9:38                     ` Joerg Schilling
2017-03-30  3:17                       ` Warner Losh [this message]
2017-03-29  6:55                 ` Peter Jeremy
2017-03-29  8:51                   ` Joerg Schilling
2017-03-28 17:51               ` Joerg Schilling
2017-03-27 20:28 ` Clem Cole
2017-03-27 20:43 ` Warren Toomey
2017-03-27 22:18   ` Kurt H Maier
2017-03-28  2:41   ` arnold
2017-03-28  5:42     ` arnold
2017-03-28  7:07     ` SPC
2017-03-28  7:30   ` Hellwig Geisse
2017-03-28 11:38   ` Derek Fawcus
2017-03-28 15:36     ` Christian Neukirchen
2017-03-28 17:28       ` Steve Simon
2017-03-28 18:19       ` arnold
2017-03-27 21:07 ` Warner Losh
2017-03-27 21:11 ` Warner Losh
2017-03-27 21:51   ` Warren Toomey
2017-03-27 21:45 ` Nemo
2017-03-27 22:22   ` Grant Taylor
2017-03-28  2:17 ` Cory Smelosky
2017-03-28  7:43 ` David du Colombier
2017-03-28  8:04 ` Jason Stevens
2017-03-28 18:07 ` Tim Newsham
2017-03-28 19:54   ` Kurt H Maier
2017-03-30 19:43 Norman Wilson

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='CANCZdfpi7NKRzOhT=9xgxstmXJVdPpcpd-MHiAMmdO0PWR5DFw@mail.gmail.com' \
    --to=imp@bsdimp.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).