From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Fri, 18 Apr 2003 23:45:11 +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 Greg KH wrote: >>When people say "hotplug" do they mean both a) and b) or only a)? > > > Both. Well, traditionally only for a), as that's all we had. The stuff > for b) will show up in 2.5.68 and beyond. I use "hotplug" very broadly ... the /sbin/hotplug infrastructure is how one part of it gets implemented, but isn't the whole story. So (a) and (b) are part of it, but so are many other things. I'd say both (a) and (b) are subsets of "kernel hotplug", which is limited to delivering events through /sbin/hotplug. We've been enlarging the number of event types the kernel supports, past the original core of USB, PCI, and network events; yet it's still the same simple "typed event" mechanism, no matter how many event types and sources use it. But if I plug a printer in to my computer, I want it to "hotplug" so that it's automatically hooked into the printing system and appears in the next printer selection dialog I pop up. (And some business customers will demand centralized policy hooks, so printer sharing is appropriately controlled.) To put it differently: hotplug is just one entree into the system administration toolset. Netlink is another one, more specialized. - 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