On Wed, 2003-08-20 at 13:36, Jim Sibley wrote:
> This bug is especially scary if you try a build in an LPAR instead of under
> VM. For operational reasons, one tends to include more DASD in an LPAR that
> is actually used (like the whole DASD subsystem) and limit the scope of the
> operational system with DASD= and IGNORE_CIO=.
We have talked about this internally ... the benefit of auto-probing is
ease-of-use; the danger is you accidentally overwrite a DASD you didn't
want to ... :)
For my internal work, I require my parm files to have an explicit DASD
parameter ...
> However, the install, if you don't specify DASD will pick the first volume
> it sees.
>
> Needless to say, I have NOT tried this on any of my LPARs.
The "hey that's not what I expected" drive appearance in disk druid was
sufficient to make me carefully evaluate things ... :)
Brock
--
Brock Organ QA Engineer borgan@xxxxxxxxxx
"That which we are, we are..." "I `em what I`em!"
-Alfred, Lord Tennyson -Popeye, Lord Sailor
_______________________________________________
Redhat-s390-list mailing list
Redhat-s390-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/redhat-s390-list
