From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Thu, 17 Apr 2003 23:50:14 +0000 Subject: Re: communicating with user login sessions 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 Havoc Pennington wrote: > Hi, > > There's this text on the hotplug web site, not sure it's up to date: > > A gap in current Linux support is that policies with any sort of > dynamic "interact with user" component aren't currently > supported. For example, that's often needed the first time a > network adapter or printer is connected, and to determine > appropriate places to mount disk drives. It would seem that such > actions could be supported for any case where a responsible human > can be identified: single user workstations, or any system which is > remotely administered. This is a classic "remote sysadmin" problem, > where in this case hotplugging needs to deliver an event from one > security domain (operating system processes) to another (desktop > for logged-in user, or remote sysadmin), and any effective response > must go the other way. At this writing, Linux doesn't have widely > adopted solutions to such problems. That particular text would still seem to be accurate ... :) I think the main thing I'd say about that site is that it's not been updated recently, or for 2.5 support. I'd love a volunteer who was interested in updating it, overhauling it, or whatever. I've added a link to D-Bus right there. > This is by no means specific to device hotplugging - there's a general > problem of delivering events from the OS out to user login sessions. > Non-hotplug events might be things like "printer queue has changed" > ... > http://www.freedesktop.org/software/dbus/ How would you speculate that a hotplug event should be delivered to the "system message bus"? I'm not quite sure how the kernel would be expected to authenticate itself, or whether it should. If there's going to be a daemon collecting kernel events, I tend to think it should be able to read them directly ... - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ 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