How Does One Re-run write_cd_rules

May 05th, 2012 - 11:10 pm ET by Martin McCormick | Report spam
This system started out as lenny in 2009 and I just upgraded
to squeeze. Most of the system is fine but I have lost both
CDROM's which used to be /media/cdrom0 and /media/cdrom1. I
didn't help anything when I accidently left a usb drive
installed so it looks like the thing to do is clean out
/etc/udev/rules.d of 70-persistent-cd.rules and start over minus
the usb drive in the hopes that I can modify the rules to get
the CDROM's back.

There is a executable file in /lib/udev called write_cd_rules
but I can't seem to find what calls it or what $DEVPATH value it
needs to run properly.

Documentation as to how all this goes together is also
lacking. Google searches produce about ten-quadrillian hits of
which precisely one is relevant but described a similar
situation in fedora and the suggested fix didn't work, here, and
all the rest are just hits on copies of write_cd_rules and the
generator rules file that write_cd_rules uses when one runs it.

Is there a way to re-run it and produce new files that
can be used as a starting point?

Thanks for all constructive suggestions.


To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120506030...0I55019167@x.it.okstate.edu
email Follow the discussionReplies 2 repliesReplies Make a reply

Replies

#1 Tom H
May 06th, 2012 - 05:00 am ET | Report spam
On Sat, May 5, 2012 at 11:00 PM, Martin McCormick
wrote:
       This system started out as lenny in 2009 and I just upgraded
to squeeze. Most of the system is fine but I have lost both
CDROM's which used to be /media/cdrom0 and /media/cdrom1. I
didn't help anything when I accidently left a usb drive
installed so it looks like the thing to do is clean out
/etc/udev/rules.d of 70-persistent-cd.rules and start over minus
the usb drive in the hopes that I can modify the rules to get
the CDROM's back.

       There is a executable file in /lib/udev called write_cd_rules
but I can't seem to find what calls it or what $DEVPATH value it
needs to run properly.

       Documentation as to how all this goes together is also
lacking. Google searches produce about ten-quadrillian hits of
which precisely one is relevant but described a similar
situation in fedora and the suggested fix didn't work, here, and
all the rest are just hits on copies of write_cd_rules and the
generator rules file that write_cd_rules uses when one runs it.

       Is there a way to re-run it and produce new files that
can be used as a starting point?



Move "/etc/udev/rules.d/70-persistent-cd.rules" to another location
and run "echo add > /sys/block/sr0/uevent".


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Archive: http://lists.debian.org/CAOdo=

Similar topics