From: jrvalverde@cnb.uam.es (José R. Valverde)
Subject: [TUHS] Sprite
Date: Mon, 31 May 2004 09:16:03 +0200 [thread overview]
Message-ID: <20040531091603.4d730f68.jrvalverde@cnb.uam.es> (raw)
In-Reply-To: <200405301319.i4UDJdOf004920@skeeve.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
On Sun, 30 May 2004 09:19:39 -0400
Aharon Robbins <arnold at skeeve.com> wrote:
> Wasn't the Symmetry a 386 based system? Could Sprite be "revived" for the
> modern PC? Just wondering ...
>
Would it make sense? Other than for historic reasons I mean.
Nowadays we have Linux, well supported, widely spread, with logging file
systems and with at least three free process migration extensions (Mosix,
OpenMosix and OpenSSI) plus Bproc. It would make more sense to pursue a
merge of these extensions in the main kernel.
Truly, Sprite would be totally unencumbered (i.e. possibly free of SCO-like
attacks) but that wouldn't preclude any deep-pocket to attempt spurious or
unfunded attacks to spread FUD if they felt they could capitalize on them.
It's true too that Sprite code (to me) is more elegant, but I have concerns
how would it look after ten years of community development and without
Ousterhout's leadership.
Not less true, having a microkernel based implementation is tempting, but
I doubt people is ready for uKernels with so much marketing pressure to make
them believe that they need to squeeze every single cycle and buy new CPUs
every so. It takes time and experience with several *different* systems,
algorithms and architectures to realize that a 10% linear speedup is most
often a meaningless achievement.
And to finish, the multi-architecture single-system image is still far
from most clusters, and noteworthy in itself, but I'm sure it would come if
more people could land their hands on more than cheap PCs for playing.
I certainly long for Sprite and would have loved to continue using it. Had
it been distributed two years earlier it might have become 'the' open system
instead of Linux. But so might have BSD had it not been for the ATT lawsuit.
Opening it might have produced the extensions and maintenance that the
original research team couldn't provide, but at the time few could imagine
what the Internet community was able to achieve.
That said, I have also pondered that same question many times, but lack the
time or resources to give it a try (sigh).
j
--
These opinions are mine and only mine. Hey, I saw them first!
José R. Valverde
De nada sirve la Inteligencia Artificial cuando falta la Natural
next prev parent reply other threads:[~2004-05-31 7: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
2004-05-31 10:26 ` Jochen Kunz
2004-05-31 7:16 ` José R. Valverde [this message]
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=20040531091603.4d730f68.jrvalverde@cnb.uam.es \
--to=jrvalverde@cnb.uam.es \
/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).