Michael Sullivan <msulli1...@gmail.com> writes:
> OK, for several years I have not had a /dev/cdrom. My workstation has
> an internal cd-rom drive, which gets mapped to /dev/hda, and an external
If you're using a recent kernel, it's probably udev which refuses to
process devices under the old ATA driver.
(I don't know if it *exactly* refuses, or if it's something else, but
the final result is what you see, no /dev/{cdrom,cdrw,...} link)
> DVD+R drive, which is mapped to /dev/sr0. When I look
> at /etc/udev/rules.d/70-persistent-cd.rules I see:
>
> camille rules.d # cat 70-persistent-cd.rules
> # LITE-ON_COMBO_SOHC-5236K (pci-0000:00:1f.1-ide-0:0)
> ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.1-ide-0:0", SYMLINK
> +="cdrom", ENV{GENERATED}="1"
...
> # LITE-ON_COMBO_SOHC-5236K (pci-0000:00:1f.1-ide-0:0)
> ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.1-ide-0:0", SYMLINK
> +="cdrom1", ENV{GENERATED}="1"
...
> # LITE-ON_COMBO_SOHC-5236K (pci-0000:00:1f.1)
> SUBSYSTEM=="block", ENV{ID_CDROM}=="?*",
> ENV{ID_PATH}=="pci-0000:00:1f.1", SYMLINK+="cdrom5", ENV{GENERATED}="1"
>
> LITE-ON_COMBO_SOHC-5236K is my internal drive, which SHOULD be mapped
> to /dev/cdrom. But it's not:
>
> camille rules.d # ls /dev/cdrom
> ls: cannot access /dev/cdrom: No such file or directory
Check also /dev/cdrom*. Maybe it got another name, as there are at least
three rules to symlink that drive (if it matched all rules, udev would
create the three links, but the third rule looks different).
> Why is it not being mapped correctly? Is the rule above not correct?
> I've tried to read tutorials about writing udev rules, but the example
> rules in the tutorials look nothing like the above rules, and I didn't
> write those. I think they were created when udev was installed...
--
Nuno J. Silva
gopher://sdf-eu.org/1/users/njsg
