[BusyBox] Modprobe passes parameters to modules only for kern el 2.6

[Fabrice Gautier]

> -----Original Message-----
> From: Erik Andersen [mailto:andersen at codepoet.org] 
> Sent: Thursday, May 05, 2005 9:37 PM
> To: Bertrand Mollinier Toublet
> Cc: busybox at mail.busybox.net
> Subject: Re: [BusyBox] Modprobe passes parameters to modules 
> only for kernel 2.6
> 
> On Thu May 05, 2005 at 08:25:52PM -0700, Bertrand Mollinier 
> Toublet wrote:
> > All,
> > 
> > I found out only recently that the modprobe applet of 
> BusyBox passes 
> > parameters to modules only for 2.6 kernels (which of course 
> is a problem 
> > for my team, as we work with a 2.4 kernel and try to pass 
> parameters to 
> > modules with modprobe...) Apparently, this was changed 
> about 8 months 
> > ago (as indicated by 
> > 
> http://www.busybox.net/cgi-bin/viewcvs.cgi?rev=9103&view=rev), but I 
> > could not find any explanations about the rationale for 
> such a change. 
> > Can anyone clarify this for me?
> 
> Noone is intentionally withholding this feature.  It is missing
> since it was never implemented.  Submit a well implemented patch
> and we'll put it in,
> 
>  -Erik

Hi,

What do you mean by it was never implemented ? Was there a problem with 2.4
before this patch ? 

My own hack was simply to remove the #ifdef and "it works for me"...(With a
2.4.26 uClinux kernel.)

I guess that would not qualify as a well implemented patch and that there is
something else behind this ... 

The insmod applet works just fine with parameters and I believe modprobe
just call the insmod applet in the end. So I don't really see what I'm
missing ?

I don't have any modules.dep or other modules files, could this be part of
the story ?

Thanks

-- Fabrice