Matt, > 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. Do you have two controllers? Because of the "churn" of moving from 31-bit to 64-bit, some folks are in the same situation you are. That is, you need both 31 and 64-bit servers depending on the workload that will be run. The redbook was written so you can have the controller (LINUX00) clone *either* a 31-bit or 64-bit SLES9, but not both. To be able to clone either, I would recommend creating a second controller. You obviously have to name it something other than LINUX00. Actually, naming the two something more descriptive like SLES9 and SLES9X might help.
> So our directory structure looks like: > > /nfs/sles9root/core9/CD?/suse/s390 and > /nfs/sles9root/core9/CD?/suse/s390x Yes, that could be a problem (this is actually one reason why the mksles9root script was coded to exit when it detects the same sles9root/ directory). I would recommend adding a layer such as /nfs/sles9 and /nfs/sles9x. Put all the .iso images in the appropriate directory and run ?mksles9root s390? from the first and ?mksles9root s390x? from the second. Then you will have two separate install trees. Hope this helps. "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 ---------------------------------------------------------------------- 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
