В Fri, 07 Mar 2014 22:15:40 +0200 Samuli Suominen <ssuomi...@gentoo.org> пишет:
> > On 07/03/14 21:57, Samuli Suominen wrote: > > [ ... ] > > > > So, make sure only 50-udev-default.rules has it's rfkill line and > > create file 70-gentoo-acl.rules with content of: > > > > SUBSYSTEM=="rfkill", TAG+="udev-acl" > > > > This would make it work with ACLs "+" if user is viewed as 'active > > = TRUE' in `ck-list-sessions` > > > > Can someone confirm? > > > > > > I don't get why 99-systemd.rules uses SUBSYSTEM=="rfkill" but someone > just posted me this: > > $ udevadm info -a --name /dev/rfkill > > looking at device '/devices/virtual/misc/rfkill': > KERNEL=="rfkill" > SUBSYSTEM=="misc" > DRIVER=="" > > So it would have to be KERNEL=="rfkill" instead of > SUBSYSTEM=="rfkill"? Would be so much easier if I had a device that > created /dev/rfkill, I wonder if that can be simulated somehow sane. > $ sudo udevadm info -q all --path /sys/class/rfkill/rfkill0 P: /devices/pci0000:00/0000:00:04.0/0000:02:00.0/usb8/8-2/8-2.2/8-2.2:1.0/bluetooth/hci0/rfkill0 E: DEVPATH=/devices/pci0000:00/0000:00:04.0/0000:02:00.0/usb8/8-2/8-2.2/8-2.2:1.0/bluetooth/hci0/rfkill0 E: ID_PATH=pci-0000:02:00.0-usb-0:2.2:1.0 E: ID_PATH_TAG=pci-0000_02_00_0-usb-0_2_2_1_0 E: RFKILL_NAME=hci0 E: RFKILL_STATE=1 E: RFKILL_TYPE=bluetooth E: SUBSYSTEM=rfkill E: SYSTEMD_WANTS=systemd-rfkill@rfkill0.service E: TAGS=:systemd: E: USEC_INITIALIZED=59720 -- Alexander Tsoy
