From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 5B9A6D2B8; Thu, 02 Jul 2026 23:20:14 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id 50A24D2A7; Thu, 02 Jul 2026 23:20:12 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_PASS,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=4.0.1 Received: from mail-4397.protonmail.ch (mail-4397.protonmail.ch [185.70.43.97]) by atuin.qyliss.net (Postfix) with ESMTPS id 436DFD2A3 for ; Thu, 02 Jul 2026 23:20:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=colbyt.com; s=protonmail; t=1783034410; x=1783293610; bh=ire9yF6ejtLJWT2AyvXYbbrFzWZ9EiRogmkGQd9JqZs=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=O+aL1E3Cw5MNKOF++w4UjXrbVJ+hvXnRSY3KKYC1UBg/JKJoa9hmRJK18Xcpfw/bD bdzwF2VbaEwej9dYhrYMdfm+Vi/4rQNf3FjNYRQjLYApdt1QL4v1UxfcyoXmiKcBq1 CqOFs2jD06B/m0pPETjy+XSvAC0GEGPV09mUctY4g0cerct0WeBnhcJUyffFH8izey ZaCT5iLPV/aE56xynDk+ApTGvw+2Oh16NfXithxYrxhlzr8mM7NMpPZ729Vu5mXtts d6CAiUTudPkLBigFQQ3LqyQDuLCOcklEoTrhb6THvON8+75s0OO4EikvuTzsZrik7H 780PG7ipBnu4g== Date: Thu, 02 Jul 2026 23:20:04 +0000 To: Alyssa Ross From: colby@colbyt.com Subject: Re: [PATCH optional] linux: use 6.18 for generic images Message-ID: In-Reply-To: <87bjcpwlse.fsf@alyssa.is> References: <20260626185509.3715326-1-colby@colbyt.com> <20260626185509.3715326-10-colby@colbyt.com> <87bjcpwlse.fsf@alyssa.is> Feedback-ID: 70977973:user:proton X-Pm-Message-ID: 92a681301f2f212ac80b29bf59e337fc4d22d6ad MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: 2MO5RUZHNN4SAWKR7BP2V5KZJEXCYI2Y X-Message-ID-Hash: 2MO5RUZHNN4SAWKR7BP2V5KZJEXCYI2Y X-MailFrom: colby@colbyt.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-devel.spectrum-os.org-0; header-match-devel.spectrum-os.org-1; header-match-devel.spectrum-os.org-2; header-match-devel.spectrum-os.org-3; header-match-devel.spectrum-os.org-4; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: devel@spectrum-os.org X-Mailman-Version: 3.3.10 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Awesome -- for my purposes I only needed a current kernel, I just was doing= that out of perceived consideration, since I was sending a major nix updat= e and going to the newest kernel. =20 All of those sets are just all the things I had to do to get to nixlatest a= nd boot native apple devices, in case you didn't have any of those update p= atches on your local. On Thursday, July 2nd, 2026 at 7:28 AM, Alyssa Ross wrote: > colbyt writes: >=20 > > Keep the generic rootfs, app VM, net VM, and installer on the linux_6_1= 8 > > package set after updating nixpkgs. > > > > This is an optional conservative variant for deployments that should st= ay > > on the Linux 6.18 LTS line instead of following linux_latest to Linux > > 7.1.1. With the new nixpkgs pin, that keeps the LTS track while updatin= g > > from Linux 6.18.2 to Linux 6.18.36. > > > > Tested with the full integration suite on Linux 6.18.36. > > > > Signed-off-by: colbyt >=20 > In Spectrum proper I'd like to stick to the latest stable kernels. > There are a few reasons for this: >=20 > =E2=80=A2 Backports, including security fixes, to older kernels are best-= effort, > and sometimes end up getting missed. > =E2=80=A2 By working with newer kernels we catch regressions faster. The= longer > it takes for a regression to be found, the more difficult it can be to > get it fixed (e.g. because there's a higher chance somebody has > started depending on the new behaviour). > =E2=80=A2 New features from new kernels! >=20 > Naturally, some specialized deployments might still prefer to pin a > kernel version, and Spectrum should facilitate this as long as it > doesn't cause undue maintenance overhead. >