From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: gentoo-user@lists.gentoo.org, Michael <confabulate@kintzios.com>
Subject: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation
Date: Tue, 16 Apr 2024 15:29:00 +0200 [thread overview]
Message-ID: <26142.32028.468334.583381@woitok.gmail.com> (raw)
In-Reply-To: Msg <2934047.e9J7NaK4W3@rogueboard> of 2024-04-16 11:15:07 +0100 from confabulate@kintzios.com
Michael,
On Tuesday, 2024-04-16 11:15:07 +0100, you wrote:
> ...
> > But this brings up two related questions:
> >
> > 1. Why does Gentoo not somehow mark LTS kernels either in the version
> > number or in the slot name? This would make it easier to prevent the
> > installation of too modern kernels.
>
> My understanding is the gentoo-sources kernels are aligned with the LTS
> upstream releases.
Right, they use the same version numbers. But you can't see from just
looking at the available "gentoo-sources" which one is LTS and which one
is not. You have to consult "https://www.kernel.org/" to get this in-
formation.
> ...
> The make oldconfig script will identify new config items not present in your
> old kernel config, show which is the default option and ask you to
> interactively select which one you prefer; e.g.
>
> SPECULATION_MITIGATIONS [Y/n/m/?] (NEW)
>
> The default option above has been identified as Y, if the devs have determined
> this is a safe default for the arch. You can hit Enter to select Y, or type
> 'n' for no, 'm' for module, or '?' to read the extended description and help
> for this option before you make up your mind.
Bingo! This is exactly the information I somehow wasn't able to find in
my early Gentoo days! You made my day :-)
Sincerely,
Rainer
next prev parent reply other threads:[~2024-04-16 13:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 17:46 [gentoo-user] Slightly corrupted file systems when resuming from hibernation Dr Rainer Woitok
2024-04-14 18:41 ` [gentoo-user] " Dr Rainer Woitok
2024-04-15 11:48 ` Michael
2024-04-16 9:04 ` Dr Rainer Woitok
2024-04-16 10:15 ` Michael
2024-04-16 13:29 ` Dr Rainer Woitok [this message]
2024-04-16 13:53 ` Arve Barsnes
2024-04-16 14:53 ` Grant Edwards
2024-04-16 15:07 ` Dale
2024-04-16 15:01 ` Dale
2024-04-16 15:14 ` Grant Edwards
2024-04-16 16:43 ` Dr Rainer Woitok
2024-04-16 19:26 ` Grant Edwards
2024-04-17 9:10 ` Michael
2024-04-17 13:52 ` Grant Edwards
2024-04-17 20:05 ` Dale
2024-04-17 20:32 ` Grant Edwards
2024-04-17 22:18 ` Dale
2024-04-17 15:50 ` Dr Rainer Woitok
2024-04-17 17:52 ` Wols Lists
2024-04-17 10:37 ` Dr Rainer Woitok
2024-04-17 10:56 ` Michael
2024-04-17 14:11 ` Grant Edwards
2024-04-17 16:11 ` Dr Rainer Woitok
2024-04-17 17:53 ` Grant Edwards
2024-04-16 10:55 ` Dale
2024-04-16 11:15 ` Michael
2024-04-16 12:48 ` Dale
2024-04-16 14:32 ` Jack
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=26142.32028.468334.583381@woitok.gmail.com \
--to=rainer.woitok@gmail.com \
--cc=confabulate@kintzios.com \
--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