From: hansolofalcon@worldnet.att.net (Gregg C Levine)
Subject: [TUHS] Sprite
Date: Sun, 30 May 2004 18:16:33 -0400 [thread overview]
Message-ID: <001301c44693$c5961260$6401a8c0@who5> (raw)
In-Reply-To: <20040530174621.3fea7782.jkunz@unixag-kl.fh-kl.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]
Hello from Gregg C Levine
Okay, now this begs the question: Can the VAX Station boot code which
is targeted to that specific system, be rewritten to accommodate the
VAX processor that SIMH emulates? I am not a good C programmer, just a
whatever comes before that. I can only offer these suggestions, and
ask these questions.
For that matter, do any of us have any of the SUN hardware that I do
know Sprite ran on? Or that VAX Station? For me, its no to all three.
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke." Obi-Wan Kenobi
> -----Original Message-----
> From: tuhs-bounces at minnie.tuhs.org
[mailto:tuhs-bounces at minnie.tuhs.org] On
> Behalf Of Jochen Kunz
> Sent: Sunday, May 30, 2004 11:46 AM
> To: tuhs at minnie.tuhs.org
> Subject: Re: [TUHS] Sprite
>
> On Sun, 30 May 2004 09:19:39 -0400
> Aharon Robbins <arnold at skeeve.com> wrote:
>
> > > There where several ports: Sun3, Sun4 / SPARC, DECstation, SPUR,
> > > Sequent Symmetry at least. Even mixed architecture clusters
where
> > > supported. See
> > > http://www.cs.berkeley.edu/projects/sprite/retrospective.html
> > Wasn't the Symmetry a 386 based system?
> Yes.
>
> > Could Sprite be "revived" for the modern PC? Just wondering ...
> Most likely no. The Sequent Symmetry machines had only one thing in
> common with a PeeCee: The Intel 80386DX chip. Everything else was
custom
> Sequent architecture.
>
> And by the way: I have hands on experience with a 8 CPU Sequent
Symmetry
> S27. It cost over 900000 DM (today about 500000 US$) in 1989 and had
a
> much slower disk and network interface as the Sun 3/260. It was an
> overpriced snail.
> --
>
>
> tschüß,
> Jochen
>
> Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2004-05-30 22:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 13:19 Aharon Robbins
2004-05-30 15:46 ` Jochen Kunz
2004-05-30 22:16 ` Gregg C Levine [this message]
2004-05-31 10:26 ` Jochen Kunz
2004-05-31 7:16 ` José R. Valverde
2004-05-31 16:58 ` Maciek Bieszczad
-- strict thread matches above, loose matches on Subject: below --
2004-05-31 10:45 Aharon Robbins
2004-05-27 18:17 Carl Lowenstein
2004-05-27 19:47 ` Jochen Kunz
2004-05-28 4:06 ` Cornelius Keck
2004-05-26 21:36 Cornelius Keck
2004-05-26 23:06 ` Kurt Wall
2004-05-27 8:16 ` José R. Valverde
2004-05-27 0:57 ` Cornelius Keck
2004-05-25 8:40 José R. Valverde
2004-05-26 4:29 ` Randy Belk
2004-05-26 8:05 ` Greg 'groggy' Lehey
2004-05-26 10:01 ` José R. Valverde
2004-05-26 12:19 ` Cornelius Keck
2004-05-26 14:15 ` José R. Valverde
2004-05-27 7:05 ` Jochen Kunz
2004-05-26 5:26 ` Gregg C Levine
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='001301c44693$c5961260$6401a8c0@who5' \
--to=hansolofalcon@worldnet.att.net \
/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).