From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Cuyle Fritzinger Date: Tue, 04 Dec 2001 22:59:14 +0000 Subject: Re: hotplug ownership/permissions Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, 4 Dec 2001, David Brownell wrote: > Sure, and I have no problem with applying it in those cases. > I've said so before and have no reason to say otherwise. > > But Scott's just described a general mechanism that doesn't > necessarily apply only in that case ... and moreover, said that > the permissions should be set AFTER the scripts that would > be triggering actions that would depend on a particular setting. > > Example, some GNOME gPhoto2 GUI starts up and then fails > because it needs a permission setting... because it's set too late! a quick clarification that i didn't make in my original post: the permissions are set after each script (in case there is a script that 'behaves badly') so that the 'next' script is guaranteed the proper permissions. the usb.agent would just make sure that the state going into each script is set properly (perm/owner). -=Scott > > > here's the logic behind this: by running every matching map entry's > > > module/script, we can guarantee that a single script won't hog the device. > > > the usb.agent will set owner/perms AFTER every script has run so that the > > > perms are guaranteed. > > I'm missing something here. Suppose two different apps want to > > assign the device to two different users? One's on the console, > > another's on a remote X display (or SSH)? > I think that for the vast majority of cases, console-user permissions > are desired. _______________________________________________ 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