public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Upgrading from 5.14 to 6.0 version
Date: Mon, 14 Nov 2022 15:05:57 -0600	[thread overview]
Message-ID: <5f196e3a-9457-4cf5-8e30-431259d41b61@gmail.com> (raw)
In-Reply-To: <tku6je$35t$1@ciao.gmane.io>

Nikos Chantziaras wrote:
> On 12/11/2022 23:37, Dale wrote:
>> Usually, I try to update about once a year.  I don't change hardware
>> much.
>
> The main reason I suggested LTS is because that, *when* you decide to
> do a @world update, you will get the latest LTS of the same main
> version you're already using. For example you'll go from 5.15.20 to
> 5.15.78. And that means you won't have to bother with an array of
> endless "make oldconfig" questions. There'll be like one or two at
> most, which is trivial to deal with.
>
> I've been using LTS kernels for years now, and I never looked back.
> "make oldconfig" usually doesn't say anything, making it a
> ridiculously fast and no-brainer update, and yet I get the latest
> bugfixes and security fixes.
>
> It just works :-)
>
>
>


Thing is, I may go a year, sometimes more, without updating the kernel. 
If I rebooted often, I could see using a LTS kernel.  If a kernel can
run for months with no problems, it's stable enough for me.  Plus my
hardware works.

I have even built a kernel but never actually booted it.  By the time I
get around to rebooting, I've had to build another kernel.  I generally
always work from a known stable config tho.  The only reason I wouldn't
is if I build a new system and have to start from scratch.  I've also
had times when I had to update because my video drivers wouldn't build
with a older kernel version that I'm running.  That doesn't happen to
often but I recall running into that at least once. 

Either way, biggest question was if there was some known breakage
between my old version and a newer version.  Maybe the one I tried just
had some weird problem that only affected me or I just missed something
during the oldconfig.  I wish I could recall the error.  Who knows on
that. 

Thanks.

Dale

:-)  :-) 




  reply	other threads:[~2022-11-14 21:06 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  6:25 [gentoo-user] Upgrading from 5.14 to 6.0 version Dale
2022-11-11 10:30 ` Peter Humphrey
2022-11-11 10:35   ` Arve Barsnes
2022-11-11 10:56     ` Wols Lists
2022-11-11 18:12     ` Laurence Perkins
2022-11-11 12:24 ` hitachi303
2022-11-11 19:18   ` Dale
2022-11-11 22:08     ` Dr Rainer Woitok
2022-11-11 14:41 ` Rich Freeman
2022-11-11 19:42   ` Dale
2022-11-11 18:04 ` Laurence Perkins
2022-11-12 12:08 ` ralfconn
2022-11-12 16:00 ` [gentoo-user] " Nikos Chantziaras
2022-11-12 18:22   ` Dale
2022-11-12 18:43     ` Mark Knecht
2022-11-12 19:13     ` Wol
2022-11-12 20:02       ` Nikos Chantziaras
2022-11-12 20:03       ` Mark Knecht
2022-11-12 21:37         ` Dale
2022-11-14 19:57           ` Nikos Chantziaras
2022-11-14 21:05             ` Dale [this message]
2022-11-14 21:44               ` Michael
2022-11-14 23:56                 ` Wol
2022-11-15  0:10                 ` Dale
2022-11-15 17:46                   ` Laurence Perkins
2022-11-15  2:36                 ` Grant Edwards
2022-11-14 21:44               ` Mark Knecht
2022-11-12 21:17       ` Rich Freeman
2022-11-21  6:10 ` [gentoo-user] " Dale
2022-11-21 12:20   ` Rich Freeman
2022-11-21 20:52     ` Dale
2022-11-21 16:11   ` [gentoo-user] " Grant Edwards
2022-11-21 16:27     ` Michael
2022-11-21 16:50       ` Grant Edwards
2022-11-21 17:24         ` Michael
2022-11-21 18:12           ` Grant Edwards
2022-11-21 19:26             ` Michael
2022-11-21 19:37               ` Grant Edwards
2022-11-21 21:30                 ` Frank Steinmetzger
2022-11-21 18:15           ` Laurence Perkins
2022-11-22 19:01             ` Wol
2022-11-21 16:58     ` Mark Knecht
2022-11-21 17:49       ` Grant Edwards
2022-11-21 19:42         ` Mark Knecht

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=5f196e3a-9457-4cf5-8e30-431259d41b61@gmail.com \
    --to=rdalek1967@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