Currently the way of doing a kernel version is just having 2.6.13 for example and then tacking on a -gentoo-r[whatever revision here] However there is only 1 way to figure out what micro version you are running. Which is reading the change log. Please at least use: 2.6.13.4 as a base and then add your revision on. I noticed that 2.6.13-r3 updated to .4 so -r5 would be 2.6.13.4-r1 in the new versioning. Why add that last .4 in? in .4 there was a security patch released: plug request_key_auth memleak (CAN-2005-3119) I read these change logs every once in a while and want to know if I'm safe from these security issues. However in order to find out if I am I not only have to do a uname -r .. but I also have to read the ebuild change log to find out at what revision was it updated to the what micro version. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Use vanilla kernel if you need this...
I do not want to use the vanilla kernel I like your patches. Why is it bad to have that little extra micro version appended? Does it horribly break your version scheme, will it confuse portage? I fail to see why this wasn't done when the kernel devs even started doing the w.x.y.z version scheme. would you do Gnome 2.6-r8 ? or kde-3.4-r3 ? how about binutils? binutils-2.15.92.0.2-r10 the extra bits don't seem to have any effect on portage it still works quite nicely. Can I at least get a better explanation other than "use vanilla kernel"
gentoo-sources kernels don't correspond to vanilla sources, these are patched with backported and other patches. See http://dev.gentoo.org/~dsd/genpatches/kernels.htm for information on relevant patches. Also see Bug 101354.
Dupe of Bug 101354. *** This bug has been marked as a duplicate of 101354 ***
