From: Colin Leroy <colin@colino.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Richard Purdie <rpurdie@openedhand.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] led-class.c permission change
Date: Sun, 6 May 2007 00:20:28 +0200 [thread overview]
Message-ID: <20070506002028.53230d56@localhost.localdomain> (raw)
In-Reply-To: <20070505224803.67f76749@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-05 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 10:49 [PATCH] led-class.c permission change Colin Leroy
2007-05-05 21:48 ` Alan Cox
2007-05-05 22:20 ` Colin Leroy [this message]
2007-05-06 12:37 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070506002028.53230d56@localhost.localdomain \
--to=colin@colino.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@openedhand.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox