modprobe broken with recursive deps

[Timo Teräs]

Mike Frysinger wrote:
> On Tuesday 05 May 2009 08:44:39 Timo Teräs wrote:
>> Mike Frysinger wrote:
>>> doing `modprobe` on any module that only has a dependency list <=1 level
>>> deep works fine.  as soon as i try to modprobe anything deeper, modprobe
>>> fails to act recursively.  so lets look at the case of `modprobe snd-pcm`
>> This was intentional. It speeds up loading time and reduces memory
>> requirements considerably.
>>
>> The proper thing is to have modules.dep to contain full dependency list on
>> it for each module. The depmod should generate a file like that (if it
>> doesn't it's a depmod bug). I think module-init-tools depmod does the same.
> 
> busybox should mirror whatever module-init-tools is doing.  if it isnt, then 
> it's a bug in busybox, or it should be an optional config option.

Smells like m-i-t changed things. Now it seems to do binary index file
for modules.dep to speed up things. I suspect for this reason it might
not do full dependency listing either.

> the m-i-t man files arent terribly clear here and my modules.dep isnt deep ... 
> will have to read the code to check
> 
>> Or did you generate modules.dep with something else?
> 
> i'm using the depmod.pl part of busybox, so there's a bug in busybox somewhere 
> here

Maybe you generated it with an old busybox depmod? That would explain it.

- Timo