From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Love Date: Fri, 27 Feb 2004 19:19:11 +0000 Subject: Re: udev - TODO update Message-Id: <1077909551.6309.5.camel@localhost> List-Id: References: <20040212234538.GC21117@vrfy.org> In-Reply-To: <20040212234538.GC21117@vrfy.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, 2004-02-27 at 12:37, Greg KH wrote: > Oh come on. You are so close to actually writing a patch that we can > use for udev that it's not even funny :) > > Care to? Yah, when I find the time. ;-) I started doing it (and wrote the previous snippet of code) around the time of the "great daemonization" so I ended up holding off. I recall I was also worried that, depending on when the permissions were parsed once we moved to a daemon, they could be a race. > Oh I agree it's something that distros will want to use. And how does > pam come into play here? Doesn't it allow us to do some of this for us? Pam's consolehelper stuff, which RH uses, can set the permissions on login. That works for preexisting devices - using a $local type thing will work for newly hotplugged devices. And hotplugged devices are an important use case: my camera should only be readable by me, for example. Robert Love ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click _______________________________________________ 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