All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@alumni.caltech.edu>
To: jdow@earthlink.net,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux on the Unisys ES7000 and CMP2 machines?
Date: Wed, 14 Mar 2001 17:43:46 -0800	[thread overview]
Message-ID: <3AB01E52.FE611677@alumni.caltech.edu> (raw)

jdow wrote:
> 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.

I just saw one of these 32 processor machines at Internet World,
and the engineer said that AIX and the successor to SCO Unix would
also run on the machine.  Perhaps the engineers doing the AIX port
are under less restrictive terms.

(When the two people he was talking to asked about Linux on the machine, 
he said "We feel Linux can't do enterprise-level stuff like this."
He got a little defensive when we questioned his judgement.)

- Dan

             reply	other threads:[~2001-03-15  1:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  1:43 Dan Kegel [this message]
2001-03-15 12:28 ` Linux on the Unisys ES7000 and CMP2 machines? Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2001-03-04 16:45 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

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=3AB01E52.FE611677@alumni.caltech.edu \
    --to=dank@alumni.caltech.edu \
    --cc=jdow@earthlink.net \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.