On 05 May 2007 at 22h05, Alan Cox wrote: Hi, > > This patch changes the led brightness file's permissions to 0666, > > so that a user's MUA can light up the mail LED without needing root > > permissions. > > NAK. > > The management of user specific temporary permissions belongs in user > space with a safe "no" default value to stop background daemons doing > silly things. Mmh, ok... My usage pattern for this is for an MUA plugin[1] that does write 1 to /sys/class/leds/asus:mail/brightness, for example, when new mail comes. The MUA typically runs as user and until now most of the handled LEDs had no such permission problems (/proc/acpi/asus/mled, /proc/acpi/acer/mailled etc). So, I've got to find a way to write into that file as user so that things automatically work. > Take a look at the various pam console management modules (and also > beat people up to get revoke() support into the kernel). So, you suggest me to link my plugin to libpam and find something that allows the plugin to write into /brightness? Thanks, [1] http://www.claws-mail.org/plugin.php?plugin=acpinotifier -- Colin
Attachment:
signature.asc
Description: PGP signature
- Follow-Ups:
- Re: [PATCH] led-class.c permission change
- From: Alan Cox <[email protected]>
- Re: [PATCH] led-class.c permission change
- References:
- [PATCH] led-class.c permission change
- From: Colin Leroy <[email protected]>
- Re: [PATCH] led-class.c permission change
- From: Alan Cox <[email protected]>
- [PATCH] led-class.c permission change
- Prev by Date: [PATCH -mm] libata-core: convert to use cancel_rearming_delayed_work()
- Next by Date: Re: Ext3 vs NTFS performance
- Previous by thread: Re: [PATCH] led-class.c permission change
- Next by thread: Re: [PATCH] led-class.c permission change
- Index(es):
 |