Description of problem: Nov 9 21:37:29 tux udevd[20486]: add_to_rules: the 'device' link is deprecated and will be removed from a future kernel, please fix it in /etc/udev/rules.d/50- udev.rules:75 Nov 9 21:37:29 tux udevd[20486]: add_to_rules: the 'device' link is deprecated and will be removed from a future kernel, please fix it in /etc/udev/rules.d/50- udev.rules:233 Nov 9 21:37:29 tux udevd[20486]: add_to_rules: the 'device' link is deprecated and will be removed from a future kernel, please fix it in /etc/udev/rules.d/50- udev.rules:235 Nov 9 21:37:29 tux udevd[20486]: add_to_rules: do not reference parent sysfs directories directly, that may break with a future kernel,please fix it in /etc/ udev/rules.d/50-udev.rules:248 Nov 9 21:37:29 tux udevd[20486]: add_to_rules: DRIVER== will change in a future relase, please use DRIVERS== in /etc/udev/rules.d/50-udev.rules:264 Nov 9 21:37:29 tux udevd[20486]: add_to_rules: do not reference parent sysfs directories directly, that may break with a future kernel,please fix it in /etc/ udev/rules.d/50-udev.rules:265 Nov 9 21:37:29 tux udevd[20486]: add_to_rules: the 'device' link is deprecated and will be removed from a future kernel, please fix it in /etc/udev/rules.d/50- udev.rules:329 Nov 9 21:37:29 tux udevd[20486]: add_to_rules: the 'device' link is deprecated and will be removed from a future kernel, please fix it in /etc/udev/rules.d/50- udev.rules:330 Nov 9 21:37:29 tux udevd[20486]: add_to_rules: the 'device' link is deprecated and will be removed from a future kernel, please fix it in /etc/udev/rules.d/50- udev.rules:331 Version-Release number of selected component (if applicable): udev-103-1 kernel-2.6.18-1.2798 How reproducible: Everytime when upgrading udev to 103-1. Actual results: Things are deprecated and will be removed from a future kernel Expected results: No deprecated stuff would be nice... Additional info: Don't you test new releases before pushing it into Rawhide? :-(
I get this too. But hey, this is development, isn't it? ;-)
We don't test... you do :) Just kidding.. :)
Although I consider those messages warnings (so things ought to work nonetheless) I no longer get device nodes made for my external USB-DVD-DW. Manually inserting usb-storage and sr-mod makes the nodes appear, however.
udev-103-2
I do have udev-103-2 installed and I am still seeing on a startup Starting udev: udevd[419]: add_to_rules: DRIVER== will change in a future relase, please use DRIVERS== in /etc/udev/rules.d/50-udev.rules:264 What is more the only rule with 'DRIVER' in it in the whole /etc/udev/rules.d directory is in line 268 of /etc/udev/rules.d/50-udev.rules and it reads: BUS=="ide", DRIVER!="ide-cdrom", ATTRS{removable}=="1", GOTO="persistent_end" Lines 264 to 267 are comments. To add to this picture /usr/share/doc/udev-103/writing_udev_rules/index.html gives explicit examples with 'DRIVER==...' and does not mention anything about 'DRIVERS'.
Using udev-103-3: Dec 9 19:47:44 tux udevd[2639]: add_to_rules: DRIVER== will change in a future relase, please use DRIVERS== in /etc/udev/rules.d/50-udev.rules:264 Dec 9 19:47:44 tux udevd[24053]: init_udevd_socket: bind failed: Address already in use Dec 9 19:47:44 tux udevd[24053]: main: another udev daemon already running
Ping?
Current rawhide (kernel-2.6.19-1.2885.fc7, udev-103-3) works for me.
This bug was CLOSED RAWHIDE and indeed now one can find in /etc/udev/rules.d/50-udev.rules: BUS=="ide", DRIVERS!="ide-cdrom", ... but documentation in /usr/share/doc/udev-104/writing_udev_rules/index.html still talks only about DRIVER and nothing about DRIVERS (not mentioning any possible differences between these two). Should that be opened as a separate bug?