Matt, It might be. I know that the s390x distribution does have a s390 directory with some 31-bit RPMs in it, and it might be seeing some sort of conflict there.
If you had been using YOU, there are a couple of log files you can look at to see what's going on: /var/log/YaST2/y2log* /var/lib/YaST2/you/youlog I don't know if they get updated when just doing a "yast -i" command or not. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Matt Gourley Sent: Monday, October 10, 2005 1:19 PM To: LINUX-390@VM.MARIST.EDU Subject: s390 and s390x directories in /nfs/sles9root/core9 All, Due to vendor issues, we here have been moving back and forth between 31-bit and 64-bit SLES9, using the LPAR to Virtual Servers Redbook as our guide. We're settled (for now) on 64-bit, after being told that this will never, ever change, that the ports and migrations we're going to move to will be on 64-bit SLES9. Of course, we're a little skeptical, so when we moved everything over to 64-bit, we kept the 31-bit rpms on LINUX00. So our directory structure looks like: /nfs/sles9root/core9/CD?/suse/s390 and /nfs/sles9root/core9/CD?/suse/s390x When I try to, for example, run 'yast -i XFree86-libs-32bit' on one of our clones, yast exits with no errors, but XFree86-libs-32bit is not installed either. Is keeping the 31-bit code an issue? Thanks in advance, -Matt ---------------------------------------------------------------------- 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
