[SOLVED] modprobe problem

Denys Vlasenko vda.linux at googlemail.com
Sun Dec 16 18:01:11 UTC 2007


On Friday 14 December 2007 13:33, Josh England wrote:
> Ok.  Running the glibc busybox under strace shows that modprobe is
> trying to run 'insmod', '/bin/insmod', then '/usr/bin/insmod', then it
> fails.  strace under the uClib compiled busybox didn't show this.
>
> Anyhow, if I create a /bin/insmod link, modprobe starts to work!  Also,
> since my PATH contains /sbin, if I run 'export PATH' then the modprobe
> also starts to work.  I'm now just putting 'export PATH' at the top of
> my init (linuxrc) script and things work fine.  This behavior must have
> changed sometime after busybox 1.2.2.1.

This is strange. PATH is not altered by modprobe, and insmod is
executed by execvp("insmod", ...) even in 1.2.2.1. So it has to use PATH
there too.

Do you have strace of "working old busybox"? Which path does it use?
--
vda



More information about the busybox mailing list