I could just scream . . .

All efforts had ended in failure. I had a call put in to the ultimate client to see who I should call at VMWare to try to get their help in resolving this mess - but no answer came back today.

"Well", I thought, "I understand you can actually uninstall udev and go back to the old fashioned /dev with a zillion drivers listed in it". So I decided to do that.

I set up to do the exact same routine I'd done the first few times, except after recompiling the 2.6.28.7 kernel I'd uninstall udev and see if I had a cdrom on reboot.

I did a fresh clean install of 5.0.4 with the defective 2.6.26 kernel. Then I set up my kernel stuff, did the menuconfig, compiled and installed the 2.6.28.7 kernel just like I'd done before.

Then I rebooted. First thing I did was "ls /dev/hd*" to confirm the CDROM wasn't there . . . . ls returned "hda"

AAAAAAAAaaaaaaaaaggggh!!

Why was it there now and it wasn't there the last 10 times I did the exact same thing?

I hate when this happens - because there's no (practical) way to know why. Can it even be done again?

My client said, "I don't give a shit - it's working - finish it up and ship it to me!"

Post #322,958 by Andrew Grygus 3/15/10 9:14:50 PM Reply	I could just scream . . . All efforts had ended in failure. I had a call put in to the ultimate client to see who I should call at VMWare to try to get their help in resolving this mess - but no answer came back today. "Well", I thought, "I understand you can actually uninstall udev and go back to the old fashioned /dev with a zillion drivers listed in it". So I decided to do that. I set up to do the exact same routine I'd done the first few times, except after recompiling the 2.6.28.7 kernel I'd uninstall udev and see if I had a cdrom on reboot. I did a fresh clean install of 5.0.4 with the defective 2.6.26 kernel. Then I set up my kernel stuff, did the menuconfig, compiled and installed the 2.6.28.7 kernel just like I'd done before. Then I rebooted. First thing I did was "ls /dev/hd*" to confirm the CDROM wasn't there . . . . ls returned "hda" AAAAAAAAaaaaaaaaaggggh!! Why was it there now and it wasn't there the last 10 times I did the exact same thing? I hate when this happens - because there's no (practical) way to know why. Can it even be done again? My client said, "I don't give a shit - it's working - finish it up and ship it to me!"
Post #322,962 by mvitale 3/15/10 10:09:55 PM Reply	In my experience..... /dev/hda is the hard drive. You know, where / and /home are. /dev/cdrom or /cdrom are more typical of CD-type devices...Sometimes /dev/sd0, maybe? -Mike "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759 Historical Review of Pennsylvania
Post #322,964 by static 3/15/10 10:27:31 PM Reply	/dev/cdrom is usually a symlink. It depends on what the block layer is presenting as as to what it needs to point to. Wade. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.
Post #322,966 by folkert 3/15/10 10:36:26 PM Reply	VMWare... /dev/sda(1,2,3,4,5,6,7,8) == near all hard drives, being SCSI and easier to emulate. /dev/hda == the "ide" cdrom.
Post #322,968 by mvitale 3/15/10 10:59:18 PM Reply	Ah-ha! I can haz little experience with vmware, and none of it recent. I'll sit corrected then. -Mike "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759 Historical Review of Pennsylvania

Welcome to IWETHEY!