Re: kmod won't execve()?

Adam J. Richter (adam@yggdrasil.com)
Sun, 12 Apr 1998 12:26:35 -0700

In article <199804121848.NAA00414@risacher.worldnet.att.net> you write:
>
>I've tried every kernel that had kmod in it (up to 2.1.95), and have
>upgraded to kmod.c.v6 as well. I've compiled with SMP and without.
>
>No matter what, on my UP pentium, kmod won't load anything, and in
>fact, won't execve() at all. For example, my (slightly modified)
>kmod.c.v6 kernel sez:
>
>Modprobe load failed - couldn't load "vfat" with "/sbin/modprobe"
>Error code -1
>
>/sbin/modprobe is version 2.1.85, and runs fine from the command
>line. If I do `echo /bin/hostname > /proc/sys/kernel/modprobe`, it
>likewise fails to execve() that also.
>
>Everything else that I've seen of this kernel works correctly, except
>getcwd().

Are you using an initial ramdisk? If so, the stock kmod in
2.1.95 and kmod.c.v6 will their root inode set to the root of the
initial ramdisk, even after the ramdisk process exits or chroots.

I posted a patch to 2.1.95 to linux-kernel yesterday that
solves this problem (look for "Subject: 2.1.95 freezes were my fault;
kmod patch"). I can also send it to you directly if you want.

Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 205
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu