Re: Slight change to daemonless kernel/kmod.c: please test

Adam J. Richter (adam@yggdrasil.com)
Tue, 28 Apr 1998 15:58:00 -0700


>Whilst testing the latest kmod, I found the following. I don't know
>whether this is a problem or a feature.

>As a user trying to execute an a.out I got:

>Apr 28 23:16:14 shawc kernel: kmod: failed to exec /sbin/modprobe -s -k
>binfmt-0064, errno = 13

>It works fine, if I try it as root, so it is some kind of permission problem.

>Does this mean that root has to modprobe binfmt-0064, because an
>ordinary user can't?

I just tried it and it works fine for me. I.e., I cannot
reproduce your problem.

kmod sets the effective and real user id of modprobe to 0, so
that is not the problem, even though errno 13 is indeed EACCESS
(from /usr/include/asm/errno.h). Maybe there is some other difference
in the environments that you compared or maybe you're doing something
with access control lists? I am mystified.

Also, make sure you are using the very latest version. I.e.,
please apply the kmod.c that I posted to linux-kernel this morning.

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