I solved my LVM problem: Using the LVM selection of the installer, nothing ever does the fdasd command for the disks used by LVM, so adding them to the LVM group fails.
To test this, I started yast with "yast &", and after activating the disks, I went back to the ssh session and executed fdasd -a /dev/dasdb, etc. Then I had the installer reread the partition tables. I used /dev/dasdb1 instead of /dev/dasdb for LVM, and when it came time to build out the dasd, everything works. Now I just need to figure out where to submit it as a bug. Our service contract is with IBM, but I'm not sure they'll accept pre-GA problems with SuSE software... -- Robert P. Nix Mayo Foundation RO-OC-1-13 200 First Street SW 507-284-0844 Rochester, MN 55905 ----- "In theory, theory and practice are the same, but in practice, theory and practice are different." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rick Troth Sent: Thursday, June 29, 2006 7:37 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES/SLED10 RC Software Available On Thu, 29 Jun 2006, Post, Mark K wrote: > Oh, one thing I forgot to note: For the mainframe, there is only the > s390x (64-bit) architecture. Anyone running on a non-zSeries system > won't be able to run SLES10. From what I gather, the same will be true > of RHEL5 when it appears later this year. Bah. I gotta say: this really bites. "Bah"? I can think of some stronger explitives. :-! -- R; ---------------------------------------------------------------------- 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
