From: Rusty Russell <rusty@rustcorp.com.au>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: 2.5.47bk2 + current modutils == broken hotplug
Date: Thu, 14 Nov 2002 14:46:51 +1100 [thread overview]
Message-ID: <20021114032456.46D742C09E@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 13 Nov 2002 12:11:01 -0800." <3DD2B1D5.7020903@pacbell.net>
In message <3DD2B1D5.7020903@pacbell.net> you write:
> The module-init-tools-0.6.tar.gz utilities (or something
> related -- kbuild changes?) break hotplug since they no
> longer produce the /lib/modules/$(uname -r)/modules.*map
> files as output ... so the hotplug agents don't have the
> pre-built database mapping device info to drivers.
Sorry, I've been feeding Linus (and lkml) slowly. It's not permenant,
I promise 8) I discussed the issue with Greg Kroah-Hartman and have
sent him a patch for examination. In the new method, external code
doesn't know about kernel datastructures.
> What's the plan for getting that back? (And module.conf
> params etc.)
The question is whether to force an /sbin/hotplug change to use the
module alias mechanism, or generate the modules.*map files at "make
modules_install" time to avoid breakage. I'm leaning towards #2, but
I haven't written it yet (should be simple).
0.7 has preliminary /etc/modprobe.conf support, but it only does
primitive aliases not options as yet. That's next on my list for
userspace, along with "modprobe -r".
> "Changes" says version 2.4.2 is fine, which appears to be wrong...
Thanks for the feedback,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-11-14 3:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 20:11 2.5.47bk2 + current modutils == broken hotplug David Brownell
2002-11-13 20:17 ` Greg KH
2002-11-13 20:40 ` David Brownell
2002-11-13 20:59 ` Jeff Garzik
2002-11-13 21:07 ` Greg KH
2002-11-13 22:45 ` David Brownell
2002-11-13 21:24 ` Jeff Garzik
2002-11-13 23:00 ` David Brownell
2002-11-14 3:46 ` Rusty Russell [this message]
2002-11-14 8:02 ` David Brownell
2002-11-14 10:01 ` Rusty Russell
2002-11-14 16:19 ` David Brownell
2002-11-14 17:42 ` Rusty Russell
2002-11-14 10:41 ` Gerd Knorr
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=20021114032456.46D742C09E@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox