Bug#245560: busybox-cvs-udeb: busybox insmod fails to pass module parameters on 2.4

[Martin Orr <martin@walnut.methody.org>]

Package: busybox-cvs-udeb
Severity: normal
Tags: d-i

The busybox insmod seems to be failing to pass module parameters into the
kernel, either with d-i's 2.4.25 (where I have to explicitly tell tulip to
use 10BaseT for my network card) or with my main system's 2.4.26.

Here is an example (the loop module gives a simple log message telling us what
parameter it received - 8 being the default):

root@henry:/lib/modules/2.4.26/kernel/drivers/block# /sbin/insmod loop.o max_loop=12
root@henry:/lib/modules/2.4.26/kernel/drivers/block# tail -n 1 /var/log/syslog
Apr 23 20:17:47 henry kernel: loop: loaded (max 12 devices)
root@henry:/lib/modules/2.4.26/kernel/drivers/block# rmmod loop
root@henry:/lib/modules/2.4.26/kernel/drivers/block# /home/l4545/src/debian-installer/trunk/installer/build/tmp/floppy/root/tree/sbin/insmod loop.o max_loop=12
Using loop.o
root@henry:/lib/modules/2.4.26/kernel/drivers/block# tail -n 1 /var/log/syslog
Apr 23 20:17:55 henry kernel: loop: loaded (max 8 devices)
root@henry:/lib/modules/2.4.26/kernel/drivers/block# rmmod loop

busybox-cvs 20040408-1 works fine.

-- 
Martin Orr
Linux Administrator,
Methodist College Belfast