Being in the middle of developing the 64-bit version of Slack/390, I can state with great assurance that you would be _much_ better off doing a fresh install. There is just too much stuff going on that is too difficult to figure out in a reasonable period of time.
What are you trying to preserve via an upgrade, versus having to redo with a new install? Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, November 26, 2004 1:24 PM To: [EMAIL PROTECTED] Subject: SLES9 31 bit upgrade to 64 bit SLES9 for S/390 (31-bit) in an LPAR > (no VM) using a shared IFL (I have one other LPAR running SLES9 31-bit) I would like to upgrade my existing 31-bit system to 64-bit. When I tried running upgrade mode, there were hundreds of conflicts and I was not sure how to resolve them. That seemed logical to me (31-bit vs. 64-bit issues) but should I delete the dependencies, ignore them, or what? Any suggestions on an approach would be much appreciated. Doug ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
