Re: [ANNOUNCE] hotplug-ng 001 release

[Roman Kagan <rkagan@mail.ru>]

On Fri, Feb 11, 2005 at 01:10:28PM -0800, Greg KH wrote:
> If you look at the hotplug scripts, they really don't need to touch
> sysfs at all.  (Note that the scsi one does, but I think we can fix the
> scsi hotplug event to solve this issue...)
> 
> So module autoload has really nothing to do with sysfs.

Just to make sure I understand what you mean: is the idea that hotplug
scripts get the device IDs through the environment variables only, and
the coldplug's responsibility is to fetch the info from sysfs and make
up the same set of environment variables to pass to hotplug?

Then why not just make the kernel (and coldplug) create an additional
environment variable with the fnmatch-able module name ready to use with
modprobe?  Given that kernel (and coldplug) have all the IDs in the nice
integer form it would be a matter of a single add_hotplug_env_var() (or
sprintf()) call per each device type, and would be even tinier that the
hotplug-ng :)

Roman.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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