On Tue, Jun 30, 2015 at 11:16 AM, James <wirel...@tampabay.rr.com> wrote: > > Folks have forgotten about 'kernel tuning'. I have deglected the linux > kernel quite a bit of late, mostly do to the rabid frequency and > non-sense (useless) chances being advanced. I have decided to only > update to 'long term support' kernels. So ideas on how to set up > masks and portage ? I guess just mask off all kernel updates and > manually unmask those long term kernel updates? Other ideas? >
I've started going a similar route with all the recent btrfs regressions that have bitten me. I'm now sticking with 3.18, and I'll likely move on to the next longterm series once it gets more than a few versions in. The Gentoo kernel team's announced plan is to have stable keywords on stable branches of the kernel, though I don't think they've promised to maintain all of them. Anytime there is a new stable branch arch teams will test before it goes stable, and after that the kernel team will release new versions straight to stable, the logic being that they're QAed by upstream and should only contain fixes for regressions. The easiest way to stick with a branch is probably to just mask anything newer. Then you should get all new releases of that branch until it is dropped. However, I'm not sure how noisy portage will be if your branch is discontinued. I've actually taken to just cloning kernel-stable.git. They keep branches for all their releases which makes it pretty easy to do a pull when you want an update, or you can just do a fetch and checkout the release tag. I also do all my builds with O=/var/tmp/linux/ so that my git checkout stays clean (and it is faster anyway writing to tmpfs). But, with git if you mess up your checkout you can always reset it. I could almost see myself switching back to gentoo-sources for kdbus though, now that they're including it (optionally). -- Rich
