Notes |
(0002362)
integrator
05-17-07 02:43
|
From linux-2.6.21.1/kernel/kmod.c, line 64:
int request_module(const char *fmt, ...)
{
va_list args;
char module_name[MODULE_NAME_LEN];
unsigned int max_modprobes;
int ret;
char *argv[] = { modprobe_path, "-q", "--", module_name, NULL };
static char *envp[] = { "HOME=/",
"TERM=linux",
"PATH=/sbin:/usr/sbin:/bin:/usr/bin",
NULL };
[--SNIP--]
So the kernel *does* set PATH before calling modprobe. What kernel version are you using? |
|
(0002363)
iggarpe
05-17-07 04:28
|
I'm using 2.6.20.11. The code snippet is the same.
Something must be wrong somewhere. Busybox's /sbin/modprobe keeps failing and I'm absolutely sure it is because the PATH is not set. I've tried to replace it by a sheel script that just does write all the environment variables to a file and still I don't see the PATH set.
I'll investigate further and get back. |
|
(0002364)
iggarpe
05-17-07 07:42
|
Back. Unable to reproduce the problem using the pristine busybox-1.5.0 sources. I still have the system in which I detected the problem and it persists.
Most probably, my fault for messing with modprobe while investigating an udevd PATH issue.
Please dismiss this bug report. |
|
(0002365)
integrator
05-17-07 08:51
|
Closing as reporter says it no longer happens. |
|