Frank, Well, then it is not supported. I just misunderstood how scsidev works. Anas Frank Steiner wrote:
Anas Nashif wrote
yes, it should. Are you having any issues?
Ok, now we tried it and it doesn't work :-) The system is a IBM pSeries on which we already installed SLES9(ppc) via autoyast, but with giving
<device>/dev/sda</device>
in the profile. That worked fine. To test if works in general with our pSeries and SLES9, we put
<device>/dev/scsi/sdh0-0c0i8l0</device>
in the profile. But then autoyast tells us "The specified device is not available on the system" (or similar, our message is in german), when it fetches and reads the profiles from the nfs server. We got the scsi device path from looking at /dev/scsi/ and running "scsidev -s" when the host was running with sles9 and from. The path is correct, because we can mount the partitions on this disk with dev/scsi/sdh0-0c0i8l0p1 -p4.
But checking the console output, I don't see any message that the installer started sth. like scsidev before starting yast, so I wonder how autoyast should know about /dev/scsi/..?
cu, Frank