On Tue, 2003-08-19 at 18:17, Richard Hitt wrote:
> The odd thing is that the Disk
> Druid (and the Autopartition method as well) comes up with /dev/dasdr as
> the disk to use, not /dev/dasda as I had hoped.
what is your "DASD=" parameter set to in your parm file? That will
affect the device -> linux device node mapping ...
> A separate annoying problem is that the disk my sysadmin assigned me was
> not virgin but
> had a copy of our UTS operating system on it. Using that disk led to
> the problem that anaconda
> could find no dasd at all to use for the install. I solved that problem
> by using the DDR program under CMS to copy a Linux CDR disk image onto
> the assigned disk.
that is a known issue we are working to fix ... :)
>
> Perhaps there's no way around these installation problems other than for
> anaconda to present
> the installer with a list of dasd and let the installer choose which one
> anaconda should use.
This is the action of the DASD= parameter ...
> I've received scant to no mail lately on this mailing-list. Is there
> another venue that is being
> used for discussion of Red Hat on S/390? Should I be sending email like
> this to another list?
it is just low traffic ... :)
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
