Re: [INFO] Kernel strict versioning

[Adrian Bunk <bunk@stusta.de>]

On Fri, Apr 08, 2005 at 01:08:28PM -0500, Franco Sensei wrote:
>...
> Actually changing a kernel results in creating a /lib/modules/version 
> directory, creating a heavy confusion for a user, especially when 
> compiling other modules outside the official kernel release: he juts 
> looses the modules and has to recompile them.
> 
> I was wondering about the feasibility of handling just a MAJOR.MINOR 
> versioning. This would be quite an increment for a user to mantain his 
> kernel. Modules can still be loaded and found. We would have a single 
> /lib/modules/2.6 being much compatible with other modules, working with 
> 2.6.x and 2.6.y without any difficulty. Also the source tree from a 
> user's point of view is much cleaner, identifying the ongoing kernel 
> much easily.
>...

This has nothing to do with versioning.

You are asking for ABI compatibility between different kernel versions.

There is no stable ABI between different kernel versions and there will 
never be one. Please read Documentation/stable_api_nonsense.txt for 
details.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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