From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: modutils 2.4.2, please test asap
Date: Mon, 22 Jan 2001 20:30:02 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98019782806809@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98018911111962@msgid-missing>
Thanks for the modutils update, Keith. Too bad this has been
such a mess to get straight -- that 2.4.0final patch caught
most folk by surprise!
> > Because the USB maintainers did not want to support backwards
> > compatibility, Linus saw no need for the patch. Which is fine, if you
> > are happy to break backwards compatibility. It should be obvious that
> > I disagree strongly with this attitude.
Put it differently: If you want to use 2.4.0-test (and prerelease)
kernels, use the 2.3.* modutils.
As it stands, we saw a bug report this morning about how 2.4 modutils
broke hotplugging with 2.2 kernels, since it created unusable (empty)
"usbmap" files ... you're not as backwards-compatible as you may
think you are!
I think it's reasonable not to want to support 2.4-test kernels;
anyone trying to use one of them has no reason to expect support.
> Isn't it true that the /sbin/hotplug support code simply doesn't
> exist in older kernels?
No; it's in the 2.2 backport (thanks to Greg) and current hotplug
scripts should work on 2.2 kernels too. If (!) people don't try to
use the 2.4 modutils ... the empty/unusable "usbmap" breaks things.
One more point on the "no *_device_id => no mapfile" side. That
can be kluged around in usermode, but it's an incompatibility.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-22 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 18:24 modutils 2.4.2, please test asap Keith Owens
2001-01-22 19:28 ` Keith Owens
2001-01-22 19:37 ` Miles Lane
2001-01-22 19:58 ` Stephen J. Gowdy
2001-01-22 20:05 ` Miles Lane
2001-01-22 20:16 ` Johannes Erdfelt
2001-01-22 20:30 ` David Brownell [this message]
2001-01-22 21:40 ` Keith Owens
2001-01-22 22:29 ` Johannes Erdfelt
2001-01-22 22:51 ` Keith Owens
2001-01-22 23:09 ` Greg KH
2001-01-22 23:21 ` David Brownell
2001-01-22 23:38 ` Miles Lane
2001-01-22 23:42 ` Keith Owens
2001-01-23 2:52 ` David Brownell
2001-01-23 3:25 ` Keith Owens
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=marc-linux-hotplug-98019782806809@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).