From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 61D9D158020 for ; Mon, 14 Nov 2022 21:45:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 56C1EE0907; Mon, 14 Nov 2022 21:44:55 +0000 (UTC) Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1AAABE089A for ; Mon, 14 Nov 2022 21:44:54 +0000 (UTC) Received: by mail-lf1-x131.google.com with SMTP id g7so21567609lfv.5 for ; Mon, 14 Nov 2022 13:44:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=aQMrc5YTdMu+RvjqvNFTcZG9UzKhHt9YWsdrCY3DSM4=; b=U9mRVSroN4AfdiyH+RsMvWR5MEoju3BCGVBOu3z2iQPvIZ0j3TT+9w1xT/zkOsy9Fa 0dqNVqH5T/3oEE9wDPVS+xplhYs+42vOJecLFyct7hiIr4KbLUyaGAe1zM+WDPiobjt2 RUSi+P+FIfEXmEhVLxSImx2aDPkzrHCyUYThUwyjaR0rf+JZovER1KFJK1HkHWjyFe2V AeIhSA4qWk04dKH0385ZrOdRBTViAVdwfbFVc2Jb0w4pTp1b4petS7OHHs6mBlxxo8gq 6h2By/quO7sZiCLBRBDXXYPgR8VVnkWEp9c65Vk2rkWZysTyHQnTPTbPMGjljEe2yMBH KVaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=aQMrc5YTdMu+RvjqvNFTcZG9UzKhHt9YWsdrCY3DSM4=; b=z6/Gc215w/e0rvgsD+TXYmohz6OGowrl43MCWe9d2CzdRdjAFHdpiy+QoVZr7Z8uDT 3h+sNrRXu6+G0zThJKrzotiMSRZ09qmGOjkGat5vNMmwFxARMxu157G/BSOUo+1JMrnn PGCElbD6Cym8dMKor9dAsK+8mLyY+NGuiyhDaf50s3bxc6KanYDZYfk4LjJp4LFWb9lI 1PX3sxFQX5sZkUF2+Ey8+yZQvAWjwlXJyOXVTmjdeEs2IfK2nRFTOJjTAslQsvYfeIta oOlnbcAFFXsCq3BTUkU50k1q4/0CWv4EOp/OI8EsC+3VgckbiNCyR8opYe0mWsk4Q2r9 AtNQ== X-Gm-Message-State: ANoB5pn9ckOq818VgjZahvXJ0bnkI34e9B0Cb1KOUIpnql9G7DO8s+rl QUKJ3rfOZhKpQv1+rmPJLamid+RPx7Bw8kLWs7GiRwo6 X-Google-Smtp-Source: AA0mqf5tupW7WTY79neYAvpgn7yVviYgcaIN0ln7bNMuePPBDQIUQww262M26GfcKLavoQvpvcv7J9Vl1fqyUeaXHH0= X-Received: by 2002:a05:6512:3b21:b0:4af:b846:2687 with SMTP id f33-20020a0565123b2100b004afb8462687mr4427570lfv.685.1668462293101; Mon, 14 Nov 2022 13:44:53 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <3418bb3d-f939-6606-7e19-5e883c198208@gmail.com> <663dc8a8-7dc2-3361-f524-3ba464fcac3b@gmail.com> <301cc78f-d97c-b965-73fd-5a8a60b09c3a@youngman.org.uk> <5428cae1-1e37-4a3b-ffe9-040b3c4a8c22@gmail.com> <5f196e3a-9457-4cf5-8e30-431259d41b61@gmail.com> In-Reply-To: <5f196e3a-9457-4cf5-8e30-431259d41b61@gmail.com> From: Mark Knecht Date: Mon, 14 Nov 2022 14:44:41 -0700 Message-ID: Subject: Re: [gentoo-user] Re: Upgrading from 5.14 to 6.0 version To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="0000000000004d328605ed7526d0" X-Archives-Salt: 5c4ebd0a-6baa-4933-b71e-84792571508b X-Archives-Hash: dcf77813bcad437f3e1f135ae9cc6248 --0000000000004d328605ed7526d0 Content-Type: text/plain; charset="UTF-8" On Mon, Nov 14, 2022 at 2:06 PM Dale wrote: > > 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 > > :-) :-) > > Dale, While I completely understand your 'reboot once a year' POV, I think you might *possibly* be missing the point Nikos and others are making. If you are on 5.14.XX you aren't currently using a LTS kernel. The LTS kernels would be the 5.10 and 5.15 series, according to kernel.org. If you don't CARE what kernel you are running then why not build 5.15.78 which is currently the most recent LTS kernel. If there are updates to that series for bug & security fixes then once you have built 5.15.78 (WHETHER YOU RUN IT OR NOT) then further updates to that series won't be a big deal and probably don't even require much of a config change or a tool chain change. It WILL be easy. You would move forward going from 5.14.15 to 5.15.78. If you don't NEED something in 6.0.5 or 6.0.8 then why bother? Once you have 5.15.78 built and installed it's there if you reboot. If you don't reboot then you'll go on building 5.15 kernels until some newer LTS kernel is named. It is truly an easy way to manage the kernel part of running Linux. Good luck, Mark --0000000000004d328605ed7526d0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Nov 14, 2022 at 2:06 PM Dale <rdalek1967@gmail.com> wrote:
>= ;
> Nikos Chantziaras wrote:
> > On 12/11/2022 23:37, Dale w= rote:
> >> Usually, I try to update about once a year.=C2=A0 I = don't change hardware
> >> much.
> >
> > = The main reason I suggested LTS is because that, *when* you decide to
&g= t; > 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 both= er with an array of
> > endless "make oldconfig" questio= ns. 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 f= ast and no-brainer update, and yet I get the latest
> > bugfixes a= nd security fixes.
> >
> > It just works :-)
> >=
> >
> >
>
>
> Thing is, I may go a yea= r, sometimes more, without updating the kernel.
> If I rebooted ofte= n, I could see using a LTS kernel.=C2=A0 If a kernel can
> run for mo= nths with no problems, it's stable enough for me.=C2=A0 Plus my
>= hardware works.
>
> I have even built a kernel but never actua= lly booted it.=C2=A0 By the time I
> get around to rebooting, I'v= e had to build another kernel.=C2=A0 I generally
> always work from a= known stable config tho.=C2=A0 The only reason I wouldn't
> is i= f I build a new system and have to start from scratch.=C2=A0 I've also<= br>> had times when I had to update because my video drivers wouldn'= t build
> with a older kernel version that I'm running.=C2=A0 Tha= t doesn't happen to
> often but I recall running into that at lea= st once.
>
> Either way, biggest question was if there was som= e known breakage
> between my old version and a newer version.=C2=A0 = Maybe the one I tried just
> had some weird problem that only affecte= d me or I just missed something
> during the oldconfig.=C2=A0 I wish = I could recall the error.=C2=A0 Who knows on
> that.
>
>= Thanks.
>
> Dale
>
> :-) =C2=A0:-)
>
>= ;

Dale,
=C2=A0 =C2=A0While I completely un= derstand your 'reboot once a year' POV, I think=C2=A0
you= might *possibly* be missing the point Nikos and others are making.

=C2=A0 =C2=A0If you are on 5.14.XX you aren't current= ly using a LTS kernel. The=C2=A0
LTS kernels would be the 5.10 an= d 5.15 series, according to kernel.org.

=C2=A0 =C2=A0If you don't CARE what kernel you = are running then why not build
5.15.78 which is currently the mos= t recent LTS kernel. If there are
updates to that series for bug = & security fixes then once you have
built 5.15.78 (WHETHER YO= U RUN IT OR NOT) then further
updates to that series won't be= a big deal and probably don't even
require much of a config = change or a tool chain change. It WILL
be easy.

=C2=A0 =C2=A0You would move forward going from 5.14.15 to 5.15.78. = If
you don't NEED something in 6.0.5 or 6.0.8 then why bo= ther?

=C2=A0 =C2=A0Once you have 5.15.78 built and= installed it's there if you=C2=A0
reboot. If you don't r= eboot then you'll go on building 5.15=C2=A0
kernels until som= e newer LTS kernel is named.

=C2=A0 =C2=A0It is tr= uly an easy way to manage the kernel part of=C2=A0
running Linux.=

Good luck,
Mark
--0000000000004d328605ed7526d0--