public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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: Wed, 17 Apr 2024 17:50:41 +0200	[thread overview]
Message-ID: <26143.61392.700212.384405@woitok.gmail.com> (raw)
In-Reply-To: Msg <4343017.ejJDZkT8p0@rogueboard> of 2024-04-17 10:10:56 +0100 from confabulate@kintzios.com

Michael,

On Wednesday, 2024-04-17 10:10:56 +0100, you wrote:

> On Tuesday, 16 April 2024 20:26:25 BST Grant Edwards wrote:
> > On 2024-04-16, Dr Rainer Woitok <rainer.woitok@gmail.com> wrote:
> > ...
> > > 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?
> > ...
>
> I am not sure the assumption "... aging hardware possibly can less and less 
> cope with newer and newer kernels" is correct.  As already mentioned newer 
> kernels have both security and bug fixes.  As long as you stick with stable 
> gentoo-sources you'll have these in your system.

But since the 6.6.* kernel is LTS,  security and bug fixes will be back-
ported into it and all is well.  And if this can't be done for some rea-
son or other,  I can still cautiously advance my entry in file "package.
mask" to the next LTS kernel.

> ...
> PS. Regarding your earlier question about different make *config commands and 
> their meaning you can check the latest make help page:
> 
> $ cd /usr/src/linux
> $ make help

Done.  Again learned something.  Thanks a lot :-)

Sincerely,
  Rainer


  parent reply	other threads:[~2024-04-17 15:50 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
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 [this message]
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=26143.61392.700212.384405@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