linux-hotplug.vger.kernel.org archive mirror
 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: Tue, 23 Jan 2001 02:52:13 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98021823127661@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98018911111962@msgid-missing>

> From: Keith Owens <kaos@ocs.com.au>
> Sent: Monday, January 22, 2001 3:42 PM
>
> On Mon, 22 Jan 2001 15:21:33 -0800, 
> David Brownell <david-b@pacbell.net> wrote:
> >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.
> 
> Tricky.  Something has to know whether to use modules.usbmap or not on
> 2.2.  This is one occasion when _not_ creating a file might be the
> correct approach. 

It'd certainly be more convenient for 2.2 based systems.


>     If I change modutils 2.4.2 to unlink existing map
> files and only create a new map file if at least one module contains
> that map, will that fix the 2.2 problem?

Yes.  Though given what you say below, I wonderif a better fix would
be to never create "modules.usbmap" if there are 2.2 style /lib/modules/
directories.  (That is, make the backwards compatibility mode cover
all the features that changed.)


> What, if anything, will break if maps files are not always created?

Likely nothing will break, but the 2.4 systems might get a bit confused
(falling back to usb.distmap)which _might_ cause something to break.
I'll have to think about it.

- Dave


> >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?
> 
> Modutils 2.4 handles both directory styles under /lib/modules/<version>,
> for backwards compatibility.  It is the kernel Makefile which sets the
> directory style for /lib/modules and there are no plans to backport the
> 2.4 style to 2.2.  AC will not take a 2.2 kernel patch that forces
> users to upgrade their user space utilities.
> 


_______________________________________________
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-23  2:52 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
2001-01-22 23:38 ` Miles Lane
2001-01-22 23:42 ` Keith Owens
2001-01-23  2:52 ` David Brownell [this message]
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-98021823127661@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).