
david writes:
> On my SuSE 10 laptop, there is no /etc/udev/devices file,
> but there are relevant files in /etc/udev/rules.d (wrapped
> to email, unfortunately):

> # grep cdrom /etc/udev/rules.d/*
> /etc/udev/rules.d/50-udev.rules:SUBSYSTEM=="block", BUS=="ide",
> DRIVER!="ide-cdrom", SYSFS{removable}="1", GOTO="persistent_end"

got this file and this entry.

> /etc/udev/rules.d/55-cdrom.rules:# cdrom links generated by YaST2

> /etc/udev/rules.d/55-cdrom.rules:SUBSYSTEM=="block",
> ENV{ID_PATH}=="pci-0000:00:1f.1-ide-1:0", SYSFS{removable}=="1",
> SYMLINK+="cdrecorder cdrom dvd"

got this file and this entry.

> I also noticed this relevant file:
> cat /dev/.udevdb/block@hdc
> N:hdc
> S:disk/by-path/pci-0000:00:1f.1-ide-1:0
> S:cdrecorder
> S:cdrom
> S:dvd
> M:22:0
> E:ID_TYPE=cd
> E:ID_MODEL=HL-DT-STCD-RWDVD_DRIVE_GCC-4242N
> E:ID_SERIAL=
> E:ID_REVISION=0201
> E:ID_BUS=ata
> E:ID_PATH=pci-0000:00:1f.1-ide-1:0

do not have this file.  i created it (with different
model, which i cobbled from dmesg), rebooted and the file
went missing again.  obviously the system is setting this
up on the fly.

> Since the rules.d file admit to being created by YaST, that would me the
> most likely source of FUBARage, but hopefully with this content you'll
> be able to unFUBAR it.

i poked about in yast and so far have found nothing
appropriate.  if i go to hardware, and cdrom drives,
both drives look set up properly -- one to /dev/hdc and
the other to /dev/sr0.  fine, but where's /dev/hdc?

think i'll just put the mknod command in boot.local and
maybe revisit the issue at the installfest.

looks to me as though more and more stuff is being hidden
from the user.  great when everything works, but ...
the world moves on.

thanks for looking,
dan

j. daniel moylan
84 harvard ave
brookline, ma 02446-6202
617-232-2360 (tel)
810-454-1823 (fax)
jdm@moylan.info
www.moylan.info

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


