RE: why is modprobe (and nothing else) exec()'d?

From: Chris Swiedler (chris.swiedler@sevista.com)
Date: Fri Oct 13 2000 - 11:24:27 EST

Next message: Harald Welte: "Re: Kernel 2.2.18 and GCC versions"
Previous message: Ivan Kokshaysky: "Re: test10-pre2"
In reply to: Harald Welte: "Re: why is modprobe (and nothing else) exec()'d?"
Next in thread: Ingo Oeser: "Re: why is modprobe (and nothing else) exec()'d?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ok, I should have thought of that ;-). I've never used modprobe directly
myself, and had forgotten that was possible. Thanks to everyone who replied.

chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Harald Welte: "Re: Kernel 2.2.18 and GCC versions"
Previous message: Ivan Kokshaysky: "Re: test10-pre2"
In reply to: Harald Welte: "Re: why is modprobe (and nothing else) exec()'d?"
Next in thread: Ingo Oeser: "Re: why is modprobe (and nothing else) exec()'d?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Oct 15 2000 - 21:00:25 EST