Re: xhotplugd ???

[David Brownell <david-b@pacbell.net>]

> http://at.rpmfind.net/opsys/linux/RPM/lycoris/build44/install/RPMS/khotplug-0.9.7-42rl.i586.html
> ftp://at.rpmfind.net/linux/lycoris/build44/rl/install/SRPMS/khotplug-0.9.7-42rl.src.rpm

I took a quick look at this.  Its "hotplugd" seems to be scanning
busses and delivering its own event reports to a UNIX socket that's
partially hidden (/var/run/.hotplugd).  Then it seems like some KDE
program (which I'll think of as "xhotplugd") interprets those reports.

Some key differences from the kernel hotplug support are:

- Since the kernel is already scanning those busses, this is
   duplicating work ... Yet Another Daemon, in this case one
   that's not necessary.  (Having one was a hotplug anti-goal.)

- It doesn't try to use the MODULE_DEVICE_TABLE information
   provided by drivers ... has its own tables to update (or more
   typically, not update) and get out of sync with the kernel.

- It doesn't even try to use the information provided through
   the /sbin/hotplug interface.  It's got its own event model.

While the user mode code might be fine (but it didn't compile for
me on RH7.3), I think it'd be better to just come up with a way
to have the /sbin/hotplug code write more standard events to such
a UNIX domain socket.

I'll be glad to see progress on hooking up hotplug events to
GUIs.  There are (unfortunately) a number of cases where users
need to make choices when devices appear.

- Dave





-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
_______________________________________________
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