On Fri, 18 Jul 2003, Oliver Neukum wrote:
We cannot prevent people from unplugging devices, which has the same consequences. So why would we make provisions to keep root from doing one more foolish thing?
Because - according to lsmod - the hcd is unused?
That seems to be how the network drivers work lately too: their use counts don't go up with "ifconfig NAME up", like they have previously done. It's not clear to me if that's a temporary flaw or a long-term change.
That is, the module refcount shown by "lsmod" doesn't seem to reflect usage other than "some other module depends on this one" ... and honestly, that makes a lot of sense to me. There are different kinds of usage, and it's been trouble that "rmmod" has only had a one-size-fits-all model.
For example, hotplug can't remove driver modules because the "lsmod" notion of "usage" is much too weak.
There should certainly be a "safe rmmod" mode that takes into account things like "that driver is bound to that hardware, even if the driver hasn't been opened yet, so don't rmmod it". And such a mode could also handle stuff like "that hcd is actually in use".
Of course, the scsi/block/... hotplug issues really should get resolved before 2.6.0 finalizes; progress has been slow.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
