| 1 |
On 08/03/14 00:50, Alexander Tsoy wrote: |
| 2 |
> ÷ Fri, 07 Mar 2014 21:17:20 +0200 |
| 3 |
> Samuli Suominen <ssuominen@g.o> ÐÉÛÅÔ: |
| 4 |
> |
| 5 |
>> - sys-apps/systemd has it's own service to handle /dev/rfkill from |
| 6 |
>> 99-systemd.rules we don't install with sys-fs/udev: |
| 7 |
>> |
| 8 |
>> SUBSYSTEM=="rfkill", TAG+="systemd", IMPORT{builtin}="path_id", |
| 9 |
>> ENV{SYSTEMD_WANTS}+="systemd-rfkill@$name.service" |
| 10 |
>> |
| 11 |
> The above rule from systemd just run a special unit which |
| 12 |
> saves/restores rfkill state across reboots. It has nothing to do |
| 13 |
> with permissions of device nodes and/or ACLs. |
| 14 |
|
| 15 |
OK. Didn't know that. Still, 40-gentoo.rules is per implementation specific, |
| 16 |
so I'll leave sys-apps/systemd handle their own. They might, or might not |
| 17 |
take action based on the results of this thread. |
| 18 |
|
| 19 |
Mainly it was to demonstrate the SUBSYSTEM=="rfkill" use that's a change |
| 20 |
to the |
| 21 |
KERNEL=="rfkill", SUBSYSTEM=="misc" I've seen in the past. |
Archives