From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation
Date: Tue, 16 Apr 2024 19:26:25 -0000 (UTC) [thread overview]
Message-ID: <uvmjd1$ntv$1@ciao.gmane.io> (raw)
In-Reply-To: 26142.43679.563313.273260@woitok.gmail.com
On 2024-04-16, Dr Rainer Woitok <rainer.woitok@gmail.com> wrote:
> Arve,
>
> On Tuesday, 2024-04-16 15:53:48 +0200, you wrote:
>
>> ...
>> Only LTS kernels get stabilised, so this information is readily available.
>
> I'm sure I don't understand this: According to "https://www.kernel.org/"
> kernel 6.6.27 is "longterm", but according to "eix" the most recent
> 6.6.* kernels are 6.6.22 and 6.6.23 which both are non-stable (well, I
> ran my last "sync" immediately before the profile upgrade, so this might
> not be current). I'm still using stable kernel 6.6.13 as my backup ker-
> nel, but this kernel is no longer provided by Gentoo. So, what precise-
> ly does LTS or "longterm" mean?
That means that all gentoo-sources stable kernels are "longterm"
kernel versions on kernel.org. It does not mean that all "longterm"
kernel versions from kernel.org are available as "stable" in
gentoo-sources.
It is a statement that "gentoo-sources stable" is a subset of
"kernel.org longterm".
It is not a statement that the two sets are identical.
In other words:
"ONLY LTS kernels get stabilized."
is a different statement from
"ALL LTS kernels get stabilized."
The former is true. The latter is not.
> But, to get back to the beginning of this discussion: if there is a
> risk that my aging hardware possibly can less and less cope with
> newer and newer kernels, should I put something like
>
> >=sys-kernel/gentoo-sources-6.7.0
>
> into file "package.mask" to stay with "longterm" 6.6.* kernels?
Yes: if you want to avoid getting upgraded to 6.8 when it gets
kernel.org "longterm" status and gentoo-sources "stable" status, then
a statement like that in in package.mask will keep you on
gentoo-sources 6.6 kernels (which are "longterm" on kernel.org).
Again: not all longterm 6.6.x kernel versions get marked as "stable"
for gentoo-sources. If you have not enabled the testing keyword for
gentoo-sources, then you'll only get the 6.6.x kernel versions that
the gentoo-sources maintainers have declared as "stable".
--
Grant
next prev parent reply other threads:[~2024-04-16 19:26 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
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 [this message]
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='uvmjd1$ntv$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.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