From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] old kernels are installed during the upgrade
Date: Wed, 3 Jan 2018 21:31:57 +0000 [thread overview]
Message-ID: <5A4D4BCD.50808@youngman.org.uk> (raw)
In-Reply-To: <ED90AAC1-1FF0-4B35-99E9-97ABAB2569ED@stellar.eclipse.co.uk>
On 03/01/18 21:21, Stroller wrote:
> Meanwhile, I've seen security vulnerabilities go unfixed for literally weeks in the bug tracker, so I don't see the significance of a vulnerability an attacker is unlikely to be able to reach. The sites I visit do not make me fear my kernel being attacked via the browser.
>
> This thread is not for arguing about security, which is an old discussion and which has been done to death. Everyone has their own opinions, and I'm not going to add any more.
>
> This thread is about how to fix OP's problem, and that's what I addressed. If you install kernels by specific version, as I suggest, then you're free to update them manually as often as you wish.
And heaven help you if you think emerging a specific version of
gentoo-sources will update the kernel you're running. Because Linux
certainly won't.
Hint: changing the current version of gentoo-sources does ABSOLUTELY
NOTHING to your running system, so why not emerge them all?
Cheers,
Wol
next prev parent reply other threads:[~2018-01-03 21:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 11:54 [gentoo-user] old kernels are installed during the upgrade Kruglov Sergey
2018-01-02 12:03 ` Alexander Kapshuk
2018-01-02 12:42 ` Mick
2018-01-02 15:59 ` [gentoo-user] " Nikos Chantziaras
2018-01-02 19:26 ` [gentoo-user] " Stroller
2018-01-02 19:47 ` Wols Lists
2018-01-03 21:39 ` Stroller
2018-01-03 21:55 ` Wols Lists
2018-01-03 22:02 ` Stroller
2018-01-03 22:09 ` Alan McKinnon
2018-01-04 6:40 ` Wols Lists
2018-01-04 8:48 ` Alan McKinnon
2018-01-03 23:43 ` Neil Bothwick
2018-01-02 20:20 ` [gentoo-user] " Kai Krakow
2018-01-02 20:28 ` Rich Freeman
2018-01-02 22:58 ` Adam Carter
2018-01-03 20:35 ` Wols Lists
2018-01-03 20:53 ` Rich Freeman
2018-01-03 21:50 ` Neil Bothwick
2018-01-04 16:02 ` Holger Hoffstätte
2018-01-04 16:10 ` Rich Freeman
2018-01-05 2:12 ` Walter Dnes
2018-01-05 2:25 ` Rich Freeman
2018-01-05 12:34 ` Walter Dnes
2018-01-05 13:08 ` Rich Freeman
2018-01-03 21:21 ` [gentoo-user] " Stroller
2018-01-03 21:31 ` Wols Lists [this message]
2018-01-03 21:43 ` Stroller
2018-01-03 21:49 ` Dale
2018-01-03 21:48 ` Rich Freeman
2018-01-03 21:53 ` Neil Bothwick
2018-01-03 22:07 ` Stroller
2018-01-03 22:11 ` Alan McKinnon
2018-01-03 22:41 ` Stroller
2018-01-03 22:47 ` Alan McKinnon
2018-01-04 2:18 ` Stroller
2018-01-03 22:51 ` Herminio Hernandez, Jr.
2018-01-03 23:41 ` Neil Bothwick
2018-01-04 2:20 ` Stroller
2018-01-02 19:44 ` Neil Bothwick
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=5A4D4BCD.50808@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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