All of lore.kernel.org
 help / color / mirror / Atom feed
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 23:21:33 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98020635701396@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98018911111962@msgid-missing>

Ah, but the hotplug utilities use it.

A pure 2.2 system (kernel + modutils) has no "modules.*map" files.
A pure 2.4 system (ditto) does have them.

But 2.2.18 kernel + 2.4 modutils will generate "modules.*map" files,
which is not compatible with the previous behavior of 2.2 modutils
with such kernels.

I forget (haven't used 2.2 in a long time) -- does 2.4 modutils
keep to the 2.2 style module tree on 2.2 kernels, or does it change
that around too?

- Dave


----- Original Message ----- 
From: Keith Owens <kaos@ocs.com.au>
To: David Brownell <david-b@pacbell.net>
Cc: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Monday, January 22, 2001 2:51 PM
Subject: Re: modutils 2.4.2, please test asap


> On Mon, 22 Jan 2001 12:30:02 -0800, 
> David Brownell <david-b@pacbell.net> wrote:
> >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!
> 
> Having found the 2.2 backport, it is obvious that it does not use _any_
> modutils support.  So an empty usbmap is perfectly correct and is
> backwards compatible.  No modules have MODULE_DEVICE_TABLE(usb) so the
> usbmap file is empty.  Where's your problem?
> 


_______________________________________________
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

  parent reply	other threads:[~2001-01-22 23:21 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
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 [this message]
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-98020635701396@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 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.