On Mon, 22 Oct 2001, Keith Owens wrote:
> When the post-install and pre-remove entries for module binfmt_misc are
> hard coded into modprobe, there is no syntax in modules.conf to prevent
> modprobe from always issuing those commands. The next time somebody
> decides that binfmt_misc needs different commands, everybody using the
> old modutils on the new kernel will break. I don't want the hassle,
> put it in modules.conf where it can easily be changed.
>
> If I can get an iron clad guarantee that binfmt_misc will never, ever
> change again then I might consider hard coding the entries in modprobe.
> BTW, I will need a signature in blood that says I can kill you if
> binfmt_misc is ever changed :).
Wait a second. Who says anything about hardcoding that into modprobe?
There is such thing as skeleton stuff for modules.conf, right?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 23 2001 - 21:00:29 EST