All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: modprobe failed: digest_null
Date: Mon, 19 Jan 2004 15:53:05 +1100	[thread overview]
Message-ID: <20040119065944.A1DA02C2A1@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 15 Jan 2004 08:30:50 -0800." <20040115083050.333bb13d.rddunlap@osdl.org>

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.

      parent reply	other threads:[~2004-01-19  6:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 21:53 modprobe failed: digest_null martin f krafft
2004-01-13 22:30 ` Randy.Dunlap
2004-01-13 22:37   ` martin f krafft
2004-01-13 22:41     ` Randy.Dunlap
2004-01-13 22:50       ` martin f krafft
2004-01-13 23:03         ` Randy.Dunlap
2004-01-13 23:38           ` David Rees
2004-01-14  0:01             ` Randy.Dunlap
2004-01-14  0:59               ` Randy.Dunlap
2004-01-14  0:08             ` martin f krafft
2004-01-14  1:05               ` David Rees
2004-01-14 23:48             ` Randy.Dunlap
2004-01-15  0:46               ` Stian Jordet
2004-01-15  8:50               ` martin f krafft
2004-01-14  1:26           ` Steve Youngs
2004-01-14  1:31             ` Randy.Dunlap
2004-01-14  8:45               ` martin f krafft
2004-01-16 15:55           ` Martin Schlemmer
2004-01-14 23:22 ` Rusty Russell
2004-01-15  8:08   ` martin f krafft
2004-01-15 16:30     ` Randy.Dunlap
2004-01-15 20:51       ` Andreas Schrell
2004-01-19  4:53       ` Rusty Russell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040119065944.A1DA02C2A1@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.