Re: modprobe is automatically calling ifup/ifconfig. Why?

[Shyamal Prasad <shyamal.prasad@sbcglobal.net>]

    "Joe" == Joe Emenaker <joe@emenaker.com> writes:

    Joe> Actually, this is happening before /etc/rcS.d/S39ifupdown
    Joe> gets run. In fact, I've pretty much traced it down to
    Joe> /etc/rcS.d/S20modutils.

    Joe> I can also repeat this from the command line like so:

    Joe>  joeslap# ifdown eth0 
    Joe>  joeslap# rmmod 3c59x

    Joe> will remove the module and ifconfig will show no eth0. Then,
    Joe> if I do:

    Joe>  joeslap# modprobe 3c59x

    Joe> then, ifconfig will show eth0 up and configured with an
    Joe> IP... seemingly with the static IP that I've got in
    Joe> /etc/network/interfaces.

    >> I suggest you modify your interfaces file so that eth0 is given
    >> a static address with no auto keyword.

    Joe> I tried that... and it still comes up.

It still comes up with the *static* IP in /etc/network/interfaces?

Well, the only thing I can guess from the above is that you have a
post-install command in your /etc/modules.conf file that is running
ifup when the module is inserted. I could be completely wrong, but
that is where I would look, assuming you have not already done this.

I'm sorry if this is no help, but this problem is something I have
never seen before.

Cheers!
Shyamal