Dave, That's the ugly part. The Red Hat installer program dynamically does mknod commands for the DASD devices _after_ you tell it which DASD you want. What I've done is pass the DASD= parameter to the initial ramdisk and kernel, start rhsetup, and then cancel out after I see the DASD drivers have been loaded (you should see the messages on the console, not in your telnet session).
Mark Post -----Original Message----- From: Dave Myers [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 7:11 PM To: [EMAIL PROTECTED] Subject: Why is insmod dasd_mod... not working on my RH 7.2 ramdisk system After I issue insmod dasd_mod insmod dasd_eckd_mod .... I do not see and /dev/dasda1 ....so my mount command to /mnt/sysimage does not work I do see the disks in /proc/dasd/devices What am I doing wrong?? Thanks, Dave
