BTW this message for 2.0.19 is that the version in the modules is 2.0.19 and
the kernel is 2.0.19 and the module will NOT load because the versions are
different.
This has happened on 2.0.1, 10, 12, 13, 14, 15, 18, 19, and 20.
This is the reason, IMO, that this is default off.
----------
From: tyson@rwii.com
To: rriggs@tesser.com
Cc: ATPLACK@scj.com; linux-kernel@vger.rutgers.edu
Subject: Re: Modules
Date: Tuesday, October 01, 1996 8:00AM
From: Rob Riggs <rriggs@tesser.com>
> On 30-Sep-96 Anthony Plack wrote:
> >Do we see the modules in Linux ever becoming a "seperate" entity so that
> >they are not so kernel specific?
>
> Do yo mean version specific? Module versioning (CONFIG_MODVERSIONS)
> overcomes this for the most part. I have a joystick module that
> I compiled quite some time ago. Since I use module versioning,
> that module loads easily in later kernels.
Why is CONFIG_MODVERSIONS defaulted to disabled? Why is it not the
standard configuration? I have been using it since it was created
and have never had any difficulty. In fact, it makes life much easier
and I can think of no reason to not use it.
Ty