Jerry, why do you think there is something wrong? If your CDROM is an IDE
cdrom then /dev/hdx is correct. In my case the cdrom is /dev/hdc. It was
always the case and /dev/cdrom is a link that is created for convinience.
Avi
--On Friday, March 09, 2001 23:52:15 -0600 Jerry Kreps
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0
Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0
Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...
I have no trouble firing YaST or YaST2, so they must be using some sort of driver on the fly.
Here is what vdir /dev/cd* shows: brw-rw---- 1 root disk 19, 128 Jan 19 02:36 /dev/cdouble0 brw-rw---- 1 root disk 19, 129 Jan 19 02:36 /dev/cdouble1 lrwxrwxrwx 1 root root 3 Feb 24 20:01 /dev/cdrom -> hdd brw-r----- 1 root disk 24, 0 Jan 19 02:36 /dev/cdu535
I suspect that YaST is using /dev/cdu535. BUT when I do: mount -t iso9660 -r /dev/cdu535 /cdrom I get the message: "mount: the kernel does not recognize /dev/cdu535 as a block device (maybe `insmod driver'?) "
I've never ventured into mk_nod territory, SuSE so help me out here. JLK
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- Avi Schwartz Get a Life, avi@CFFtechnologies.com Get Linux!