From: Jon Smirl <jonsmirl@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and sysfs permissions
Date: Fri, 20 May 2005 14:06:24 +0000 [thread overview]
Message-ID: <9e47339105052007065a473806@mail.gmail.com> (raw)
In-Reply-To: <9e47339105051915025188e535@mail.gmail.com>
On 5/20/05, Greg KH <greg@kroah.com> wrote:
> Nope, the kernel is. You must have provided enough memory pressure to
> push the file out of the dcache, and then when you went to look at it
> again, it was created on the fly from scratch again, with the proper
> permissions (as the kernel thinks the files have.) Nice to see it's all
> working properly :)
>
> > Can udev control sysfs permissions (I though it only controlled the
> > device permissions).
>
> No, only the kernel can control sysfs permissions.
We were planning on having PAM assign ownership of the video device
and sysfs attributes to the logged in user. I need read/write access
to the sysfs attributes but it need to be restricted to whoever owns
the device.
What's the right way to implement this?
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_idt12&alloc_id\x16344&opÌk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-05-20 14:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 22:02 udev and sysfs permissions Jon Smirl
2005-05-19 22:10 ` Kay Sievers
2005-05-20 4:33 ` Greg KH
2005-05-20 14:06 ` Jon Smirl [this message]
2005-05-20 18:33 ` Greg KH
2005-05-20 21:11 ` Jon Smirl
2005-05-20 21:26 ` Jon Smirl
2005-05-20 21:27 ` Greg KH
2005-05-20 21:40 ` Jon Smirl
2005-05-20 21:40 ` Greg KH
2005-05-20 21:41 ` Jon Smirl
2005-05-20 21:53 ` Jon Smirl
2005-05-20 21:54 ` Greg KH
2005-05-20 21:56 ` Greg KH
2005-05-20 22:07 ` Kay Sievers
2005-05-20 22:09 ` Greg KH
2005-05-26 23:09 ` Greg KH
2005-05-27 12:44 ` Maneesh Soni
2005-05-27 16:39 ` Jon Smirl
2005-05-27 21:51 ` Greg KH
2005-05-28 5:06 ` maneesh
2005-05-28 5:08 ` maneesh
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=9e47339105052007065a473806@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.