RE: version mismatch in modules--Permanent solution?

nathan.zook@amd.com
Fri, 10 Sep 1999 12:39:23 -0500

??? I'm talking about the name/directory collision you get when you have
multiple builds of the same version of the kernel. This happens, for
instance, whenever a newbie installs Linux & then tries to recompile the
kernel. What I think I am suggesting is adding an extension (to
EXTRAVERSION?) for each build to guarantee that collisions are avoided.

Nathan

> -----Original Message-----
> From: Keith Owens [SMTP:kaos@ocs.com.au]
> Sent: Friday, September 10, 1999 12:18 PM
> To: Zook, Nathan
> Cc: linux-kernel@vger.rutgers.edu
> Subject: Re: version mismatch in modules--Permanent solution?
>
> On Fri, 10 Sep 1999 11:11:20 -0500,
> nathan.zook@amd.com wrote:
> >It seems to me that the solution is to have the version number
> >changed on each build (i.e.: 2.2.5-15-build1) so that module collisions
> >don't occur.
>
> Already covered by genksyms. Select the config option "Set version
> information on all symbols for modules" and you will not be able to
> load modules from one kernel into another. It catches all sorts of
> mismatches, not just version number.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/