Re: [RFC] Kernel version numbering scheme change

From: david
Date: Fri Oct 17 2008 - 21:20:19 EST

On Fri, 17 Oct 2008, Steven Noonan wrote:
I believe some of Adrian's concerns are valid. Userspace programs will
indeed break, largely because some depend on build-time and run-time
checks for the kernel version being >=2.6.0 or >=2.4.0 and so forth.

things that do this sort of check would work just find with version 8.10.0 or 2008.10.0

the ones that would fail would be ones that made assumptions about the number (it can only have X digits in this position, I don't need to check the '2', only the '4' vs '6', etc). anything that does this sort of thing is broken already, and will fail at some point in the future, even without a radical numbering change.

suspect the best way to prove userspace breakage would be to make a
branch of the kernel with a new versioning scheme (8.10, 2008.10,
whatever) and use that as the installed kernel while building a Gentoo
system. I suspect you'd see massive breakage.

I suspect that you won't see anything noticable. you don't need to make a branch of the kernel, just edit the kernel source to change the version.

I think a version numbering system change would be OK (though I
wouldn't very much -like- it), so long as there was a way for
userspace software to be able to differentiate between a kernel with
the old versioning system and the new versioning system.

one nice thing about the year-based numbering (be it 8.x or 2008.x) is that all the numbers in the new numbering scheme are > any numbers in the old numbering scheme. so all you need to do is to check for > whatever version added the feature you need.

I think perhaps a better option in the long run is to start a v2.7
tree and figure out some Cool New Stuff(tm) to implement, keeping
consistency with the current versioning scheme.

Red Herring, the Cool New Stuff is happening now, no 2.7 needed.

David Lang
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at