a partial fix was the following.. although it is still buggy
ls -l /dev/cdrom
protection 3 date "ASSOSATION"
lrwxrwxrwx 1 root root 3 Dec 21 9:16 /dev/cdrom -> hdc
using ASSOSIATION which happens to be hdc
I can do the following
mount /dev/hdc /mnt/cdrom
and iit mounts
well nearly.. you see its not really hdc anymore its hdd......
so I have to use
mount /dev/hdd /mnt/cdrom
and it mounts...???
although it says block devioce /dev/hdd is write protected, mounting readonly.. like I could write anyway.... although it would be interesting to see what happens if I enable wriite on hte device.. .. my burer is on another box that does its stuff fine it seems.. so yah that fixed it...
so IF the device show up in initial hardware check.. then it should be on a device point somewhere so if you try to mount them all using the
mount /dev/[devicename hdahdbhdc etc..] you should be able to mount it.. although if you blindly try mounting everything ... you may ... if it isnt protected remount a already mounted system as something else.. so.... just try the ones that you know arn't already mounted.. like for instance your root mount most certainly already will be.. .anyway
note you cant open the cdrom whuile it is mounted ...... although if you umount /mnt/cdrom you can open it .. so IT WORKS.. well almost......
you see once you read the device point /mnt/cdrom .... you can't umount it... cause /mnt/cdrom:device is busy....... and it sounds like it is spinning...
so you can't stop it ok hold on it stopped spiinng lets see..
ok it stops and you can open it but it takes around a minute
.... hardware with personality.. wheres my shotgun
note befor you can open it after it stops spinning you still have to umount it.
so yah it seems to be a fix... unless thats the way its suppose to work and all the turorials are maddening propaganda.. anyway
It may be that my fstab reads the hdc while it is hdd so if I change hdc to hdd on my /dev/cdrom line in fstab it may fix it??????