From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 14 Apr 2006 14:49:28 +0000 Subject: Re: Simple Rule Now Broken in udev089 Message-Id: <20060414144928.GA5137@vrfy.org> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Apr 14, 2006 at 12:34:42AM +0000, Robert Kennedy wrote: > >On Wed, Apr 12, 2006 at 11:17:08PM +0000, Robert Kennedy wrote: > >> >On Wed, Apr 12, 2006 at 09:11:43PM +0000, Robert Kennedy wrote: > >> >> >On Tue, Apr 11, 2006 at 09:49:43PM +0000, Robert Kennedy wrote: > >> >> >> > >> >> >> For awhile I have been using the following simple rule to create a > >> >> >> persistent symlink for my removable CDRW burner: > >> >> >> > >> >> >> KERNEL="scd0", SYMLINK="cdrwiter" > >> >> >> > >> >> >> I placed this rule in 10-local.rules inside the /etc/udev/rules.d/ > >> >> >> directory. > >> >> >> > >> >> >> It used to work in previous version of udev but now it does not > >work. > >> >> >udev > >> >> >> is still creating the /dev/scd0 node but not the /dev/cdwriter > >node. > >> >> >> > >> >> >> Any ideas on what might be happening. Has anything changed in > >udev > >> >> >089? > >> >> > > >> >> >No, something like this works for me. But you should always use += > >to > >> >> >add a new symlink to the list, otherwise you reset all earlier added > >> >> >ones. Maybe there is a later rule that overwrites that one? > >> >> > > > > >> >> Thanks for the tip Kay. I tried changing the rule to: > >> >> > >> >> KERNEL="scd0", SYMLINK+="cdwriter" > >> >> > >> >> and then doing a udevstart but it did not work. I still get a > >/dev/scd0 > >> >> node but not a /dev/cdwriter node. Very strange. I only have this > >> >one > >> >> rule in 10-local.rules. 10-local.rules should be the first file > >> >processed > >> >> in /etc/udev/rules.d/ > >> > > >> >Are sure you have a scd* kernel device and not a sr*? > >> >What does: > >> > ls -l /sys/block > >> >show? > > > >> Thanks Kay. I think we are getting close. See the following: > >> > >> [root@myarch ~]# ls -l /sys/block > >> total 0 > > > >> drwxr-xr-x 3 root root 0 2006-04-12 16:58 sr0 > >> > >> [root@myarch ~]# ls -l /dev/sr* > >> ls: /dev/sr*: No such file or directory > >> > >> [root@myarch ~]# ls -l /dev/sc* > >> brw-rw---- 1 root optical 11, 0 2006-04-12 19:08 /dev/scd0 > >> > >> [root@myarch ~]# ls -l /dev/sg* > >> crw-rw---- 1 root optical 21, 0 2006-04-12 19:08 /dev/sg0 > >> > >> Even though the kernel shows it as a sr0 device, the /dev/sr0 is not > >being > >> created but instead /dev/scd0 is being created. Strange. > > > >Maybe you have a rule like Fedora is using, which may probably > >better be converted to be symlink: > > # rename sr* to scd* > > KERNEL="sr[0-9]*", BUS="scsi", NAME="scd%n" > > > >> I tried changing the rule to > >> KERNEL="sr0", SYMLINK+="cdwriter" > >> > >> and did a usevstart but that did not work either. > >> > >> I think I have a more fundamental problem to address -- i.e why is the > >> /dev/sr0 not being created. > > > >Try: > > udevtest /block/sr0 > > > >Kay > > > [root@myarch ~]# udevtest /block/sr0 > udev_rules_get_name: rule applied, 'sr0' becomes 'scd0' You have a rule somewhere to rename the default kernel name to scd*, that's why sr* never gets created. Kay ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel