FS#25024 - [cdemu-daemon] 60-vhba.rules causes udev warning
Attached to Project:
Community Packages
Opened by Jan Alexander Steffens (heftig) - Tuesday, 05 July 2011, 09:57 GMT
Last edited by Ray Rashif (schivmeister) - Wednesday, 21 March 2012, 15:48 GMT
Opened by Jan Alexander Steffens (heftig) - Tuesday, 05 July 2011, 09:57 GMT
Last edited by Ray Rashif (schivmeister) - Wednesday, 21 March 2012, 15:48 GMT
|
Details
The rules file contains NAME="%k", which is ignored by udev
and causes a warning.
Suggestion: Remove the pair. Doesn't seem to impact functionality. |
This task depends upon
Closed by Ray Rashif (schivmeister)
Wednesday, 21 March 2012, 15:48 GMT
Reason for closing: Fixed
Additional comments about closing: Update rolled in testing.
Wednesday, 21 March 2012, 15:48 GMT
Reason for closing: Fixed
Additional comments about closing: Update rolled in testing.
1) The warning doesn't show up in dmesg or everything.log and I couldn't find a udev specific log
2) I can't find the rule file for the vhba module, it's definitely not in /etc/udev/rules.d/
There's not only /etc/udev/rules.d but also /lib/udev/rules.d where the vhba file resides.
It has the strange permissions of:
-rwxr-xr-x 1 root root 72 Oct 18 20:11 60-vhba.rules
while all other files there have:
-rw-r--r-- 1 root root 46 Nov 5 00:30 60-rfkill.rules
maybe this could be fixed in one swoop.
I don't understand why we need two udev rule directories.
has to be changed to
KERNEL=="vhba_ctl", NAME="vhba_ctl", MODE="0660", OWNER="root", GROUP="cdemu"
otherwise cdemud@session-bus wont work ;)
Anyway custom rules go to /etc, system ones (provided by packages) go to /lib. That's all really. The permission is probably a leftover from upstream, no big deal (doesn't make a difference here if it's executable or not).