public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] old kernel on Gentoo
Date: Thu, 18 Jun 2020 16:02:51 -0400	[thread overview]
Message-ID: <CAGfcS_mTLP16qktOwx2QDZa1gAUnuo+TUFgZvjmWj2OD3wbsEg@mail.gmail.com> (raw)
In-Reply-To: <f938bc21-7302-256d-92f5-eb6371b439c3@verizon.net>

On Thu, Jun 18, 2020 at 3:35 PM james <garftd@verizon.net> wrote:
>
> I use a 3.18.40 kernel, currently, on one of my AMD systems. It has
> thousands of source build packages, not only from portage but many others.

Keep in mind that you're running a non-longterm kernel, which means
that if there is a known regression or security issue in your kernel,
a kernel update to fix it wouldn't be provided upstream.

If you were running 3.16 or 4.4 you would get these updates.  If you
plan to stick with a kernel for a very long time you should try to
pick one that is designated as a longterm kernel.  3.16.85 was
released just a week ago.  It obviously doesn't get very frequent
updates, but if something important comes along they'll release a fix.
I'd have to check the timelines but you might have unmitigated Spectre
vulnerabilities in that kernel.

Also, you mention AMD.  If you happen to be using a Ryzen processor
there were a number of updates to the kernel to better support it.  I
forget which kernels have these but if you don't have those patches
you'd probably benefit from an upgrade.  If you have a pre-Ryzen CPU
then that won't matter much.

I completely agree that you can get away with a longterm kernel and
there are a lot of reasons for doing so.  I just recommend sticking
with one that actually is supported.

-- 
Rich


  reply	other threads:[~2020-06-18 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 16:52 [gentoo-user] old kernel on Gentoo Raffaele BELARDI
2020-06-17 17:36 ` J. Roeleveld
2020-06-17 19:45   ` Michael
2020-06-18 15:45     ` Raffaele BELARDI
2020-06-17 18:44 ` David Haller
2020-06-18  6:16 ` Gerrit Kuehn
2020-06-18 19:35 ` james
2020-06-18 20:02   ` Rich Freeman [this message]
2020-06-18 20:47     ` james
2020-06-21 10:31   ` Raffaele BELARDI
2020-06-30 14:34     ` Sid Spry
2020-07-01  7:32     ` Gerrit Kuehn
2020-07-01  8:35       ` karl
2020-07-02 21:55     ` james
2020-06-30  8:29 ` Andreas K. Huettel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGfcS_mTLP16qktOwx2QDZa1gAUnuo+TUFgZvjmWj2OD3wbsEg@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox