On Sat, 27 Oct 2001 11:25, Paul Cox wrote: | On Thursday, Oct 25, 2001, Paul Rodr�guez wrote: | > Thanks, Joe. I understand what you mean (I think), but the problem | > is my machine doesn't have a cdrom0 anywhere. It has a | > /dev/cdroms/cdrom4 instead. But just before my last reboot it was | > /dev/cdroms/cdrom3 . I'm not sure why the number is changing. | | More specifically, this is a devfs problem. As root, remove the files | in /lib/dev-state (but leave the directory). After rebooting, | /dev/cdrom should be correct. | | One consequece of this however, is that if you have networking setup | for VMware (vmnet* devices), you'll have to run vmware-config.pl again. | This fixed it for me. | | Also, I'm not real sure how permenent of a solution this is, as I | haven't been using devfs since because of the security advisory.
How about trying the "devfs=nomount" option in lilo.conf. This most likey has nothing to do with your cdrom but you could give it a go. I had to do that to stop a whole lot of boot/error messages I was getting about a kernel bug and the zip, floppy, cdrom, cdrw drives being already registered (although everything was working OK anyway). Mandrake were already aware of the problem I was having a little while back and they recommended editing the lilo.conf file. They were working on fix then, so I guess by now that they will have already fixed the problem in a more recent kernel. skinky -- But what ... is it good for? (Engineer at the Advanced Computing Systems Division of IBM, 1968, commenting on the microchip)
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
