From: "J. Dow" <jdow@earthlink.net>
To: "Miles Lane" <miles@megapathdsl.net>,
"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: Linux on the Unisys ES7000 and CMP2 machines?
Date: Sun, 4 Mar 2001 22:41:34 -0800 [thread overview]
Message-ID: <022f01c0a540$b7366820$0a25a8c0@wizardess.wiz> (raw)
In-Reply-To: <3AA27137.3020600@megapathdsl.net>
From: "Miles Lane" <miles@megapathdsl.net>
> I noticed that this article mentions that Unisys has
> no plans to port Linux to it's "cellular multiprocessor"
> machines. So, I am wondering if anyone is working
> on this independantly.
Miles, if these babies are the 32 processor monsters that UniSys
has been making recently there IS interest to get Linux on it.
But the people I know who have mentioned "interest", mostly from
a curiosity standpoint, have their hands neatly tied by Microsoft.
Ya see, the developers at UniSys have NT source licenses so they
can develop the HALs for the monsters. Microsoft insists that they
spend a considerable time away from OS development before working
on another OS. So, no Linux port is in the offing, I suspect. The
people who KNOW the machine are not allowed to do it. And I can
guarantee you that the machines are not well documented at the
level a person making an NT port would need. (As an aside it seems
the UniSys guys know more about how to debug HALs without fancy
ICEs than the MS guys. At least the amount of travel between
Mission Viyoyo and Redmond suggests it.)
{^_^} Joanne "Too many years in a DoD environment" Dow, who has
put a whole string of two's together to figure out the
above from clues laid by her HAL developer partner.
jdow@earthlink.net
next prev parent reply other threads:[~2001-03-05 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 16:45 Linux on the Unisys ES7000 and CMP2 machines? Miles Lane
2001-03-04 16:52 ` David Weinehall
2001-03-04 20:44 ` J Sloan
2001-03-05 0:09 ` Gerhard Mack
2001-03-05 6:46 ` J. Dow
2001-03-05 6:41 ` J. Dow [this message]
2001-03-15 1:43 Dan Kegel
2001-03-15 12:28 ` Rik van Riel
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='022f01c0a540$b7366820$0a25a8c0@wizardess.wiz' \
--to=jdow@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.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).