Re: [ANNOUNCE] hotplug-ng 001 release

[Erik van Konijnenburg <ekonijn@xs4all.nl>]

On Sat, Feb 12, 2005 at 01:45:19AM +0300, Roman Kagan wrote:
> On Fri, Feb 11, 2005 at 11:06:57PM +0100, Erik van Konijnenburg wrote:
> > For an old version of the idea, see
> > 
> > 	http://bugs.debian.org/cgi-bin/bugreport.cgi?bug(4294
> 
> It looks like the same thing can be achieved by adding a flag to
> modprobe to print the list of modules it would load, in the style of
> modprobe -vn, but with no regard to whether any of them are already
> loaded (should be a few lines of code).  Then just run coldplug with
> such a flag passed to modprobe.
> 
> Or am I missing the point?

That's correct, but not the whole story.

Modprobe handles dependencies: in order to load module ata_piix,
you need libata.  That's a necessary part of the solution.
Coldplug walks sysfs and finds interesting stuff to feed to
the modules.pcimap parser and modprobe.  Also necessary.

What's extra is that mkinitrd needs to do this not for
the running kernel but for the next kernel, that it needs to
do so only for the modules needed to get the root operational,
and that it needs to coordinate that with support for non
hotplug devices like LVM and mdadm.

Regards,
Erik


-------------------------------------------------------
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