The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jon Forrest <nobozo@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: [TUHS] Life at UC Berkeley (was Unix on Zilog Z8000?)
Date: Wed, 22 Jan 2020 13:04:23 -0800	[thread overview]
Message-ID: <1f0a98ad-b7f2-fe79-79f1-441800b21b55@gmail.com> (raw)
In-Reply-To: <e44f0597-bff4-2cdd-8ca5-be394eb2e434@mhorton.net>



On 1/22/2020 9:00 AM, Mary Ann Horton wrote:

> Even before Zilog's ZEUS, Onyx came out with a microwave oven-sized box 
> based on the Z8000. They loaned one to Berkeley, and it was my first 
> home computer when I took it home to port the tools. 

As someone who played a very minor role at UC Berkeley, I thought
I'd amplify this a little. It was amazing how the various vendors
would happily lend (or give) equipment to UC Berkeley. I don't
know how things were at the other top CS schools, but at Berkeley
I found that if I needed something, telling my faculty boss/mentor
would often make the item appear.

For example, I did an early port of Postgres to Windows NT using
a DEC PC with 16MB of RAM. With such a small amount of RAM this
was excruciatingly slow but I made enough progress to show Mike
Stonebraker. He then talked to his friends in industry and all of
a sudden a MIPS(!) box with 64MB of RAM showed up. I was then able
to get the port to the point where it could run the Wisconsin benchmark.

Something similar happened when the group wanted to port an early
version of Postgres95 to Solaris (it had been developed on DEC Alphas 
running OSF/1). Mike said to write up a proposal to Sun that he'd sign
and then send in, which I did. Soon after a couple of Sparcstation 10s
(or 20, I don't remember) showed up and the port was done.

There other systems research groups at UCB in the 90s also were
the happy recipients of all kinds of great hardware. The limiting factor
for such donations was usually finding space to house them. The end
result was that the RAID, Risc, and Postgres groups weren't slowed down
by lack of hardware.

I have no idea what it's like today. Eric Allman, would you care to
comment?

Jon Forrest


  reply	other threads:[~2020-01-22 21:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 17:52 [TUHS] Unix on Zilog Z8000? Jon Forrest
2020-01-21 18:13 ` Steve Nickolas
2020-01-21 18:27   ` William Pechter
2020-01-21 18:15 ` Henry Bent
2020-01-21 18:20   ` Larry McVoy
2020-01-21 21:48     ` Nigel Williams
2020-01-21 22:00       ` Henry Bent
2020-01-21 22:36         ` Derek Fawcus
2020-01-21 22:35     ` Jason Stevens
2020-03-15 18:40       ` Cornelius Keck
2020-03-16  0:28         ` Wesley Parish
2020-03-16 22:02           ` Derek Fawcus
2020-01-21 18:32   ` William Pechter
2020-01-21 21:24   ` Jon Forrest
2020-01-21 18:28 ` Clem Cole
2020-01-21 21:07   ` Heinz Lycklama
2020-01-21 21:32   ` [TUHS] Onyx (was Re: Unix on Zilog Z8000?) Derek Fawcus
2020-01-22  8:18   ` [TUHS] Unix on Zilog Z8000? Arrigo Triulzi
2020-01-22 17:00 ` Mary Ann Horton
2020-01-22 21:04   ` Jon Forrest [this message]
2020-01-23  2:08   ` Erik Fair
2020-01-22 19:55 ` Andreas Hein
2020-01-23 12:01   ` Oliver Lehmann
2020-01-25  1:46     ` [TUHS] Dhrystone Benchmark (was: Unix on Zilog Z8000?) Oliver Lehmann
2020-01-25  1:49       ` Oliver Lehmann
2020-01-25  2:29         ` Warner Losh

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=1f0a98ad-b7f2-fe79-79f1-441800b21b55@gmail.com \
    --to=nobozo@gmail.com \
    --cc=tuhs@minnie.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).