| 1 |
On Fri, Mar 07, 2014 at 09:17:20PM +0200, Samuli Suominen wrote: |
| 2 |
> - sys-apps/systemd has it's own service to handle /dev/rfkill from |
| 3 |
> 99-systemd.rules we don't install with sys-fs/udev: |
| 4 |
> |
| 5 |
> SUBSYSTEM=="rfkill", TAG+="systemd", IMPORT{builtin}="path_id", |
| 6 |
> ENV{SYSTEMD_WANTS}+="systemd-rfkill@$name.service" |
| 7 |
> |
| 8 |
> - so this is about sys-fs/udev (and perhaps, sys-auth/consolekit for ACLs) |
| 9 |
> - since the udev .rules are not application specific, we should control |
| 10 |
> it from sys-fs/udev's /lib/udev/rules.d/40-gentoo.rules |
| 11 |
> - sys-fs/udev leaves it to root:root as: |
| 12 |
> |
| 13 |
> KERNEL=="rfkill", MODE="0664" |
| 14 |
> |
| 15 |
> - third party packages like mate-bluetooth, gnome-bluetooth install both |
| 16 |
> their own udev .rules to adjust /dev/rfkill to plugdev: |
| 17 |
> |
| 18 |
> KERNEL=="rfkill", GROUP="plugdev", MODE="0664" |
| 19 |
> |
| 20 |
> So I'd like to propose some unification: |
| 21 |
> |
| 22 |
> I don't have a system with /dev/rfkill unfortunately to test this, but I |
| 23 |
> believe we should add this to 40-gentoo.rules and create group 'rfkill': |
| 24 |
> |
| 25 |
> SUBSYSTEM=="rfkill", GROUP="rfkill", MODE="0664" |
| 26 |
|
| 27 |
This doesn't make much sense: the group should be plugdev. |
| 28 |
|
| 29 |
It's only understandable when we read your last mail, about a |
| 30 |
not-yet-implemented split plugdev idea. In the interim, please |
| 31 |
keep it to plugdev, as other packages and the admin expect. |
| 32 |
|
| 33 |
> And this line would go as /lib/udev/rules.d/70-gentoo-acl.rules (as the |
| 34 |
> original filename in upstream ConsoleKit is 70-udev-acl.rules): |
| 35 |
> |
| 36 |
> SUBSYSTEM=="rfkill", TAG+="udev-acl" |
| 37 |
> |
| 38 |
> Any thoughts? |
| 39 |
|
| 40 |
Seems KERNEL might be right. |
| 41 |
|
| 42 |
-- |
| 43 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |
Archives