| 1 |
÷ Fri, 07 Mar 2014 22:15:40 +0200 |
| 2 |
Samuli Suominen <ssuominen@g.o> ÐÉÛÅÔ: |
| 3 |
|
| 4 |
> |
| 5 |
> On 07/03/14 21:57, Samuli Suominen wrote: |
| 6 |
> > [ ... ] |
| 7 |
> > |
| 8 |
> > So, make sure only 50-udev-default.rules has it's rfkill line and |
| 9 |
> > create file 70-gentoo-acl.rules with content of: |
| 10 |
> > |
| 11 |
> > SUBSYSTEM=="rfkill", TAG+="udev-acl" |
| 12 |
> > |
| 13 |
> > This would make it work with ACLs "+" if user is viewed as 'active |
| 14 |
> > = TRUE' in `ck-list-sessions` |
| 15 |
> > |
| 16 |
> > Can someone confirm? |
| 17 |
> > |
| 18 |
> > |
| 19 |
> |
| 20 |
> I don't get why 99-systemd.rules uses SUBSYSTEM=="rfkill" but someone |
| 21 |
> just posted me this: |
| 22 |
> |
| 23 |
> $ udevadm info -a --name /dev/rfkill |
| 24 |
> |
| 25 |
> looking at device '/devices/virtual/misc/rfkill': |
| 26 |
> KERNEL=="rfkill" |
| 27 |
> SUBSYSTEM=="misc" |
| 28 |
> DRIVER=="" |
| 29 |
> |
| 30 |
> So it would have to be KERNEL=="rfkill" instead of |
| 31 |
> SUBSYSTEM=="rfkill"? Would be so much easier if I had a device that |
| 32 |
> created /dev/rfkill, I wonder if that can be simulated somehow sane. |
| 33 |
> |
| 34 |
|
| 35 |
$ sudo udevadm info -q all --path /sys/class/rfkill/rfkill0 |
| 36 |
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 |
| 37 |
E: |
| 38 |
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 |
| 39 |
E: ID_PATH=pci-0000:02:00.0-usb-0:2.2:1.0 E: |
| 40 |
ID_PATH_TAG=pci-0000_02_00_0-usb-0_2_2_1_0 E: RFKILL_NAME=hci0 |
| 41 |
E: RFKILL_STATE=1 |
| 42 |
E: RFKILL_TYPE=bluetooth |
| 43 |
E: SUBSYSTEM=rfkill |
| 44 |
E: SYSTEMD_WANTS=systemd-rfkill@×××××××.service |
| 45 |
E: TAGS=:systemd: |
| 46 |
E: USEC_INITIALIZED=59720 |
| 47 |
|
| 48 |
-- |
| 49 |
Alexander Tsoy |
Archives