OT : systemd-udev issue in CentOS 8.5 / Rocky Linux 8.5 / RHEL 8.5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



   
   Sorry for being a bit off topic here but I'm hoping some of the clever people on this 
list can help me out with a systemd-udev issue here.I'm hoping this is a solved issue in
fedora that maybe hasn't made its way upstream yet.

 I have a custom usb devive that I want a certain group of users to have full access to when
it is plugged in . For CentOS 6 & 7 I just add a rule to  /etc/udev/rules.d  like

SUBSYSTEM=="usb", ATTR{idVendor}=="03eb", ATTR{idProduct}=="2017", GROUP="atmel", MODE="666"

and Bob is your uncle. The created usb device ( /dev/bus/usb/.../...  gets permissions 666 as
user root and group atmel .

 However, I cannot get this to work the same way with CentOS 8 / Rocky Linux 8 / ( RHEL 8 )
and I cannot figure out why not. The device in /dev/bus/usb is being created but only  root
can access it as the ownersip is set to root:root and the mode to 664 . The logs report an :
unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1 ( or similar depending
on the port used ) and  systemd-udev  retuns :  invalid SUBSYSTEM operation  which doesn't
tell me a lot.

 Removing the MODE and GROUP from the rule makes the error messages go away but ownership and
permissions are set to the default root and 664

 Trying to replace MODE and GROUP ith a RUN=+some_script also fails ( with or without
including the ACTION=="add" keyword. The script never starts as far as I can tell.

 Anybody knows what is going on here ? Does systemd-udevd not have root permissions ?????
I can of course set the mode as user root or use sudo but really ?

 systemd is version 239 which is probably outdated by fedora standards but it is what comes
with RHEL 8.5 clones.

                                  peter

 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux