From: Greg KH <gregkh@linuxfoundation.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Can udev manage /sys/class/leds
Date: Sun, 05 Jan 2014 03:45:31 +0000 [thread overview]
Message-ID: <20140105034531.GD22595@kroah.com> (raw)
In-Reply-To: <52C86320.4040208@c-s.fr>
On Sat, Jan 04, 2014 at 08:38:08PM +0100, christophe leroy wrote:
> Hi,
>
> I've never used udev, and would like to know if it could be the solution
> for changing permission on /sys/class/leds/ attributes.
Why would the permissions need to be changed? What would you change
them to, and what would that be based on?
> I can change permissions and ownership at startup for existing files but
> new attributes created during runtime (for instance delay_on and
> delay_off when changing the trigger to blinking) are created with root
> permission only.
> I need /sys/class/leds/ attributes owned and permitted to users of group
> 'led'.
>
> Can udev manage that ?
Yes it can tell other programs to do that, look at how the console owner
is handled by the system to give proper ownership of audio and other
device nodes when it is determined it is valid to do so.
thanks,
greg k-h
prev parent reply other threads:[~2014-01-05 3:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 19:38 Can udev manage /sys/class/leds christophe leroy
2014-01-05 3:45 ` Greg KH [this message]
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=20140105034531.GD22595@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).