Messages in this thread | ![/](/images/icornerl.gif) | | From | Rusty Russell <> | Subject | Re: modprobe failed: digest_null | Date | Mon, 19 Jan 2004 15:53:05 +1100 |
| |
In message <20040115083050.333bb13d.rddunlap@osdl.org> you write: > On Thu, 15 Jan 2004 09:08:15 +0100 martin f krafft <madduck@madduck.net> wrot e: > > | also sprach Rusty Russell <rusty@rustcorp.com.au> [2004.01.15.0022 +0100]: > | > Upgrade module-init-tools to 0.9.14 or one of the 3.0 -pres. > | > | diamond:~# modprobe -V > | module-init-tools version 3.0-pre5 > > Yes, and I'm using 0.9.14 and seeing similar messages.
Yes, as several people have pointed out. I *did* briefly make the change so -q always returned "success", but had to revert it because it caused infinite loops in some legitimate configurations (thanks to Jamie Lokier for reporting this).
With the change to default to idemptent behavior (modprobe foo when foo is already installed silently "succeeds" unless --first-time is specified), the definition of -q can be safely changed to mean "ignore this if you've never heard of it").
This is done in 3.0-pre6, now available.
BTW, if you had fairly complex modules.conf, you should regenerate modprobe.conf for the 3.0 releases: some cases have changed.
Rusty. -- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. - 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/
| ![\](/images/icornerr.gif) |