That way you can do things like adding devices on one hub while removing them from another one -- concurrently.
Obviously you could do such a thing, but where is the benefit? Contention is not an issue here. The simplest solution seems best to me.
Contention can be an issue. A related point is that getting rid of as many "single points of failure" (in this case, single khubd thread) as possible is one of the most general ways to make systems more reliabile.
Maybe _you_ don't ever need to reboot systems when khubd has wedged everything beyond recovery, but I sometimes do... :)
- Dave
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
