modprobe woes

[Tito]

On Tuesday 05 August 2008 23:02:11 Vladimir Dronnikov wrote:
> > Well, the Vladimir's code is not module-init-tools compatible
> 
> Non-small ("normal" by Bernhard) modprobes have to collect their data
> from a bunch of wide-spreaded files with loosely defined syntax. They
> have to engage linked-lists (which consumes memory by itselves) of
> strings, firstly read and then xstrdup()ed. Then "normal" modprobes
> use hardly a percent of collected data to perform actual module
> loading.
> 
> What is proposed in small modutils is to precollect hardly-editable
> data (hardcoded aliases, etc.) in format convenient for the following
> parsing. Small modprobe have to only turn spaces into nulls and the
> linked-list is ready! Any editable stuff is put separately into
> /etc/modules on a per-module basis. The only time-consuming operation
> is generation of modules.dep.bb file (similar to depmod). Consecutive
> attempts to load modules are dirt cheap. No need to bother with
> spacings, tokenization and uncommenting.
> 
> What is wrong with the idea? Just give it a try, folks!
> 

Hi,
what happens if some third party modules are compiled/added
to system after modprobe precollected his data?

Ciao,
Tito