From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Smirl Date: Fri, 20 May 2005 21:40:05 +0000 Subject: Re: udev and sysfs permissions Message-Id: <9e47339105052014405ff6ae73@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: > > That would make things simpler for driver writers if more devices are > > going to follow this model. >=20 > I think you are going to be pretty unique here, as no one else has come > up with a situation yet that requires this. If the mantra about sysfs attributes being superior to IOCTLs is true, then anyone who converts to sysfs attributes is going to run into this problem. In the IOCTL model permission obviously follows the owner of the /dev device. There is no parallel for this in the sysfs model. This is making me want to switch everything back to the IOCTLs since they are still in place. I see how group/user sysfs attributes can control things, but there should some better way to achieve control. That feels awfully clunky to me. >=20 > thanks, >=20 > greg k-h >=20 --=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