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) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 7A0BC158020 for ; Sat, 12 Nov 2022 21:17:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 50995E090E; Sat, 12 Nov 2022 21:17:14 +0000 (UTC) Received: from mail-yw1-f178.google.com (mail-yw1-f178.google.com [209.85.128.178]) (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 0B579E08A2 for ; Sat, 12 Nov 2022 21:17:13 +0000 (UTC) Received: by mail-yw1-f178.google.com with SMTP id 00721157ae682-376596ae449so73318137b3.5 for ; Sat, 12 Nov 2022 13:17:13 -0800 (PST) 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=jCj5ptdNa7TlslZVgPjWJEbqlSjyqG09KnCOYiktmsQ=; b=ND1vbz58K8h2S0g7MTfNoQVf/P/NsBWaNLRWunGVncxbp4HAnq3LT9iBXiLOXPsg9x RsHLzzRu9Jru7W34jno1Hz7LBap1f4sdzmuwHKU44AyFf6l8iEN4NjDiDG4Cukt8axSF uMXTCyrzT94yMhh6PiMwl7ERThSNXI5ws0POYaBKdsBDBEF6SOpJzeN78EmA61KAwPxj MiDs61rSqLeu8JEF9TUACLzu8o/MyQvSlSMj1IvVzqWvrwIyy5+3kGqhc2diqd/J79pK qB7XZzDr1KhR2k5vBtEFcSXFfJ5Oq4mjNsrAcAu/ERyT/JXqfMN8xQr5KQT6Lb5bfIh0 2qFA== X-Gm-Message-State: ANoB5plvwfGaPUMv4ACXSLXHknIJR8By2TpU7eaxRrCOT4lA7S3CXOQF BjAXcwQ0Yu9MfUPSYHvyejpOYtDVyskgznb5nsD5Ip0UwlA= X-Google-Smtp-Source: AA0mqf7FWpWfkPteeM4rqALrWX7LNlDbrdl0UhhuJyU3YiQmde71NnRE9Pn5R2yrXNJJOX8doi63zgiT3t0gKJLZxkI= X-Received: by 2002:a81:556:0:b0:378:5e3a:8fad with SMTP id 83-20020a810556000000b003785e3a8fadmr7334680ywf.78.1668287832812; Sat, 12 Nov 2022 13:17:12 -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> In-Reply-To: <301cc78f-d97c-b965-73fd-5a8a60b09c3a@youngman.org.uk> From: Rich Freeman Date: Sat, 12 Nov 2022 16:17:02 -0500 Message-ID: Subject: Re: [gentoo-user] Re: Upgrading from 5.14 to 6.0 version To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 7fd178c6-4d3a-4c95-8492-c1a648ab711b X-Archives-Hash: e4583ea47fd0d5af52a78a0eca6ce3e2 On Sat, Nov 12, 2022 at 2:13 PM Wol wrote: > > The idea behind stable kernels is great. The implementation leaves a lot > to be desired and, as always, the reason is not enough manpower. > Two things: first, LTS kernels aren't the same as stable kernels. Dale has been running stable kernels, and gentoo-sources kernels are all stable kernels. Second, I've been running LTS kernels for years without issue. I got into them due to running zfs/btrfs/nvidia. ZFS and nvidia are out of tree modules, and they tend to lag in support for the latest stable branches, so it is a constant battle if you want to run stable. If you run LTS they just work. When I was running btrfs I wanted to stick to LTS mainly because btrfs was constantly breaking things in new releases, which like every other subsystem are introduced in new branches. That was a while ago and maybe btrfs is more stable today. If you run anything out of tree though LTS is a much easier target. Aside from that, new kernel options are almost never added within LTS branch releases, so I just run make oldconfig and I'm done. You do get the rare change, and it is very easy to manage those. The downside is if you want some new kernel feature you won't get it, and you might need to update for support for new chipsets/CPUs if you're upgrading. That isn't a big deal to manage as I don't do it often. I can't remember the last time an LTS kernel blew up on me, but I never rush out to update a kernel the day it is released. Occassionally I do see a regression fixed and it tends to happen fairly quickly. All that said, it would be nice if the kernel had more of a QA process. I think the kernel has basically deferred all of that to distros, which means by running an upstream kernel I get none of it. The upstream kernel config defaults are also less than ideal, which is something distros also manage. -- Rich