Sandy, 'cause you're a dolt _is_ a valid answer, it's just not a very polite or informative one! :)
You can't do an insmod on a system that is running off real DASD because the DASD driver has to be compiled into the kernel, not as a module. (It's kind of hard to load the DASD driver so that you can mount the DASD so that you can load the DASD driver so that... You get the idea.) On a running 2.2 system, the only way to add/remove DASD is to update the parmfile, re-run silo, and re-boot. On a 2.4 system, it can be done dynamically. Since I believe you're trying to use a SuSE 7.0 system to install the Red Hat 7.2 system, then I would have to say you're looking at a reboot. Mark Post -----Original Message----- From: Gelbard, Sandy [mailto:[EMAIL PROTECTED]] Sent: Friday, March 22, 2002 3:01 PM To: [EMAIL PROTECTED] Subject: insmod: dasd: no module by that name found Hello, Does anynone know why I might receive the following error when trying to add an additional dasd vol to my system ? ('cause you're a dolt.. is not a valid answer ;) # insmod dasd dasd=33a2 insmod: dasd: no module by that name found I have added volumes before, but that was during the initial install phase. Thanks, SG..
