Neither of these are feasible, sorry.
Well, part of the reason why is that we're functionally "stuck" on 2.6;
a prefix which really has lost all meaning.
It might open up the question if we shouldn't just do a Solaris and drop
the leading 2 (so the next kernel would be 6.33) or call the kernel
after that 3.0 instead of 2.6.34, and then 3.1 instead of 2.6.35.
-hpa
--