Upgrade to SLES10 (s390x from s390)
It used to be the case that there was not a supported upgrade path from SLES 31-bit to 64-bit addressing modes. Is that still the case? Has anyone performed a SLES9 SP3 s390 - SLES10 s390x upgrade in place, or is trying this still more trouble than its worth (i.e. install clean and be done with it)? We have no SLES10 yet, just planning ahead. The most descriptive thing I can find right now is: http://www.novell.com/documentation/sles10/index.html?page=/documentatio n/sles10/sles_admin/data/cha_upgrade.html, which says nothing about going from one addressing mode to the other. Thanks, ~ Daniel -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Upgrade to SLES10 (s390x from s390)
It used to be the case that there was not a supported upgrade path from SLES 31-bit to 64-bit addressing modes. Is that still the case? Yes. Upgrade-in-place has never worked across architecture boundaries, and s390-s390x is an architectural boundary. is trying this still more trouble than its worth (i.e. install clean and be done with it)? Yes. You *really* don't want to have to hunt down all the possible weird library/link things. Safer (and easier) to just build a new virtual machine. You did document what you did, right...? 8-) -- db -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Upgrade to SLES10 (s390x from s390)
David Boyes wrote:
It used to be the case that there was not a supported upgrade path
from
SLES 31-bit to 64-bit addressing modes. Is that still the case?
Yes. Upgrade-in-place has never worked across architecture boundaries,
and s390-s390x is an architectural boundary.
is trying this still more trouble than its worth (i.e. install clean
and
be done with it)?
Yes. You *really* don't want to have to hunt down all the possible weird
library/link things. Safer (and easier) to just build a new virtual
machine. You did document what you did, right...? 8-)
One of the things that can happen between releases is that a package
gets dropped, maybe the function's provided in a new package, maybe not.
Think of imapd that RH dropped after RHAS; an upgrade from RHAS 2.1 to
RHEL{3,4} might leave imapd in place.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Please do not reply off-list
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
