From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Smirl Date: Fri, 20 May 2005 14:06:24 +0000 Subject: Re: udev and sysfs permissions Message-Id: <9e47339105052007065a473806@mail.gmail.com> List-Id: References: <9e47339105051915025188e535@mail.gmail.com> In-Reply-To: <9e47339105051915025188e535@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On 5/20/05, Greg KH 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 :) >=20 > > Can udev control sysfs permissions (I though it only controlled the > > device permissions). >=20 > 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? --=20 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=16344&op=CCk _______________________________________________ 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