View previous topic :: View next topic |
Author |
Message |
Marcih Apprentice
Joined: 19 Feb 2018 Posts: 213
|
Posted: Mon Feb 26, 2018 8:17 pm Post subject: Gentoo sources in stable branch |
|
|
Us boring and non-adventurous folk who still haven't moved our entire systems to testing branch have been stuck on the 4.9 kernel tree since December last year. Are there any news on continuing moving along with the upstream Linux releases? What was wrong with the 4.12 and 4.14 versions? What's happening with the frantic kernel releases over at kernel.org? Didn't it use to be like an update semi-annually? |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8935
|
Posted: Mon Feb 26, 2018 8:29 pm Post subject: |
|
|
Use 4.14 if you want to, the stable badge does not have any meaning for kernel sources except 'bugs will get preferential treatment'. Use whatever kernel is required for your hardware, or your needs, as long as it is kept up to date. 4.12 is dead for a long time already, 4.14 is the current LTS line and surely will be 'stabilised' at some point. |
|
Back to top |
|
|
Marcih Apprentice
Joined: 19 Feb 2018 Posts: 213
|
Posted: Mon Feb 26, 2018 8:58 pm Post subject: |
|
|
asturm wrote: | the stable badge does not have any meaning for kernel sources except 'bugs will get preferential treatment'. |
Ah, good to know, thanks for that info.
asturm wrote: | 4.14 is the current LTS line and surely will be 'stabilised' at some point. |
I'm following the Linux kernel releases (read: I'm subscribed to the RSS feed and occasionally look at it) and 4.15.6 has been marked as stable yesterday. Is 'Long Term Support' just a code-word for "safe to use" and 'stable' a code-word for "we can't guarantee it won't brick your machine :^)"? |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8935
|
Posted: Mon Feb 26, 2018 9:07 pm Post subject: |
|
|
For upstream, each release is a stable release. LTS means 4.14 will not stop at 4.14.12-something (it is in fact at 4.14.22 already) but will get security and bugfixes for a number of n years and climb up as high 4.14.100 or more.
There is no such thing as a guarantee and I have had issues with kernel versions as high as ~3.4.75 or ~3.4.100 because mistakes happen, but no stabilising process by Gentoo would have ever caught that, simply because it is impossible to test for all hardware out there, and all we can do is declare 'has probably been run without major bugs for a long enough time'. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21600
|
Posted: Tue Feb 27, 2018 3:40 am Post subject: |
|
|
To elaborate on asturm's explanation, kernels that are not declared LTS tend to be abandoned by GregKH shortly after he starts maintaining the next higher stable series. "Short" sometimes provides overlap of one or a few releases, but you usually won't see him maintaining 4.x.y after 4.(x+1).y has had several releases. In some cases, someone else steps up to maintain it afterward, but usually no one does. Contrast that with LTS which, as asturm says, gets years of backports and a fairly high number of releases before it is retired. |
|
Back to top |
|
|
charles17 Advocate
Joined: 02 Mar 2008 Posts: 3664
|
Posted: Tue Feb 27, 2018 5:27 am Post subject: |
|
|
Marcih wrote: | Is 'Long Term Support' just a code-word for "safe to use" and 'stable' a code-word for "we can't guarantee it won't brick your machine :^)"? |
See https://www.kernel.org/category/releases.html |
|
Back to top |
|
|
benchaney n00b
Joined: 28 Dec 2017 Posts: 30
|
Posted: Tue Feb 27, 2018 10:03 pm Post subject: |
|
|
Is there a straight forward way to setup portage to always install the latest bugfix release on a given minor branch? |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8935
|
Posted: Tue Feb 27, 2018 10:05 pm Post subject: |
|
|
Same as you would do with any other ebuild.
=sys-kernel/gentoo-sources-4.14* |
|
Back to top |
|
|
toralf Developer
Joined: 01 Feb 2004 Posts: 3922 Location: Hamburg
|
Posted: Wed Feb 28, 2018 3:46 pm Post subject: |
|
|
benchaney wrote: | Is there a straight forward way to setup portage to always install the latest bugfix release on a given minor branch? | No, but this works:
Add a sources atom to /etc/portage/package.provided, clone the Git repository of Linus' tree, add the stable repository of Greg as a remote one, initially archive+unpack the sources to something like /usr/src/linux-4.x, and follow the stable tree via Quote: | git diff v4.15.6..v4.15.7 | (cd /usr/src//linux-4.x; patch -p1) && cd /usr/src/linux-4.x && make && make modules && make install |
|
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21600
|
Posted: Thu Mar 01, 2018 2:18 am Post subject: |
|
|
If you don't use any packages that demand configured kernel sources, that can be simplified by not using /usr/src at all. Use out-of-tree builds with the source pointing to the Git repository, then you don't need a spare exported copy of the kernel sources. |
|
Back to top |
|
|
|