Fwd: as/400 / linux / lpar-

[Portal39@xxxxxxx]

--
--
[ Picked text/plain from multipart/alternative ]



--
From: Portal39@aol.com
Full-name: Portal39
Date: Sat, 1 Jun 2002 09:48:11 EDT
Subject: Fwd: as/400 / linux / lpar
To: leif@leif.org, midrangeL@midrange.com
X-Plaintext:  Picked text/plain from multipart/alternative

--
--
[ Picked text/plain from multipart/alternative ]
Guys  this  is  a needless debate
IBM did Partial LPARS for the newer processors, which is a good  and long
term business investment. you  believe it is prudent to  try to run on an
older processor family; have at it and the risks it brings  No complains
allowed  should it go  bad

Me, I will stick with what has been proven to work under the warrany

A. Ports
--
From: "Leif Svalgaard" <leif@leif.org>
To: <midrange-l@midrange.com>
References: <000001c20953$30cef400$6501a8c0@ne.client2.attbi.com>
Subject: Re: as/400 / linux / lpar
Sender: midrange-l-admin@midrange.com
Precedence: bulk
Reply-To: midrange-l@midrange.com
Date: Sat, 1 Jun 2002 06:11:14 -0500

From: Andy Nolen-Parkhouse <aparkhouse@attbi.com>
> IBM is so intent on pushing Linux that I think if they could have easily
> made it available on older processors, they would have.

What would IBM rather have: 1) a customer running Linux (and remember
that the issue is not Linux but fractional LPARs) on an older box, or 2)
a customer buying a new box because fractional LPARs (according to
Glen saves you a LOT of money)?
I think 2) and thus it makes sense for IBM to claim that fractional LPARs
require a new box (and to back up the claim with a suitable software
prevention scheme). But as I said before, maybe there *are* new
instructions in the newer processors and the hypervisor uses those
(maybe out of convenience rather than necessity). Just someone
tell me WHICH new instruction(s).
I don't buy the argument that "IBM says that a new processor is
needed, ergo new instructions must be present and used". I would
buy the argument "IBM says that instruction XYZ is needed for
fractional LPARs, ergo you need a new box".


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.