> Couple of things: I noticed that Adam added the '-s' option to the
> modprobe command line, which logs data to syslog. Maybe something is
> going wrong with this.
That was not the problem. It is being caused by the code which attempts
to force modprobe to run with the same permissions and filehandles as
init. If you comment out the call to use_init_file_context() in
exec_modprobe(), the problem vanishes and all is well.
Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu