You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2022. It is now read-only.
NOTE - the 3.14.y kernel series is now end-of-life. It will not be
receiving any more updates and should no longer be used at all.
Please use 4.4 if you want a LTS kernel that will last for another year,
or even better yet, just use the normal stable releases as those will
always contain the latest fixes and updates.
It seems like the only sensible thing to do is switch the next SD kernel to 4.4.32. There should be no problems with doing so, as Ubuntu Trusty is now on the 4.4 kernel series itself.
The text was updated successfully, but these errors were encountered:
Ubuntu Trusty is now on the 4.4 kernel series itself.
Where do you get that information from, @fowlslegs? Running a dist-upgrade on a trusty box tops out at 3.13, so it looks to me like Canonical is maintaining the 3.13 for the 14.04 LTS release. Gathered from a Trusty box:
$ aptitude show linux-generic-lts-trusty | grep Version
Version: 3.13.0.121.131
$ aptitude show linux-generic-lts-xenial | grep Version
Version: 4.4.0.81.66
We'd have to do significant QA for SecureDrop before transitioning to the 4.x series.
By default, the 14.04.5 point release will ship with a newer 4.4 Linux kernel from Ubuntu 16.04, and a matching X.org stack. This is based on the 4.4.0 Extended Upstream Stable Kernel Release. The purpose of providing a newer kernel in the 14.04.5 point release is for hardware enablement. For more information regarding the 14.04.5 LTS Hardware Enablement Stack, please refer to:
From https://lkml.org/lkml/2016/9/11/28 (emphasis mine):
It seems like the only sensible thing to do is switch the next SD kernel to 4.4.32. There should be no problems with doing so, as Ubuntu Trusty is now on the 4.4 kernel series itself.
The text was updated successfully, but these errors were encountered: