Bug#270087: initrd-tools: BUSYBOX=yes -> no insmod so modprobe broken!

[Alex Owen <owen@cus.org.uk>]

Package: initrd-tools
Version: 0.1.74
Severity: normal

When building an initrd with busybox included /sbin/modprobe is a
symlink to busybox. However busybox modprobe appears to call insmod to actually
insert the modules. Which is fine except that there is no insmod on the
initrd so no modules can be loaded and the boot fails!

I guess the solution is either 
1) to symlink /sin/insmod to /sbin/insmod.modutils which is on the initrd 
or 
2) to include insmod in the build of busybox and then (I think???) that the 
   mkinitrd scripts will symlink /sin/insmod to busybox. 

Alex Owen

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (400, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-k7
Locale: LANG=C, LC_CTYPE=C

Versions of packages initrd-tools depends on:
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  cpio                          2.5-1.1    GNU cpio -- a program to manage ar
ii  cramfsprogs                   1.1-6      Tools for CramFs (Compressed ROM F
ii  dash                          0.5.1-3    The Debian Almquist Shell
ii  fileutils                     5.2.1-2    The GNU file management utilities 
ii  util-linux                    2.12-3     Miscellaneous system utilities

-- no debconf information