Yann E. MORIN wrote:
> Evert,
>
> On Monday 24 September 2007 21:41:06 Evert Meulie wrote:
>> Eehh, that is exactly what I did. My command was:
>> insmod -f bs.ko
>> (bs.ko was present in the current directory)
>> insmod: -f.ko: no module by that name found
>>>> Usage: insmod [OPTION]... MODULE [symbol=value]...
>>>> Options:
>>>> -f Force module to load into the wrong kernel version
>
> Rings a bell here...
>
> If you enable 2.4 support, insmod will try to mimick the behavior of insmod
> from mainstream modutils.
>
> If you disable 2.4 support (and obviously enable 2.6), then insmod will mimick
> the behavior of mainstream module-init-tools. insmod from module-init-tools
> does _not_ have a -f option.
>
> What kernel version are you running: 2.4 or 2.6 ?
> - If 2.4, then you mis-configured BusyBox (afaics).
> - If 2.6, then you can not force-load a module (afaik).
Hmm, then it sounds like I'm in trouble... :-/
My kernel is 2.6.16.18.
I even tried a 3rd option, concluded from your information, and enabled support
for BOTH 2.4 and 2.6
kernel, but to no avail...
Hmm, looks like I will have to get a hold of the people who wrote that module
and work something out...
Thanks for your help! :)
Regards,
Evert
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox
