patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: colby@colbyt.com
To: Alyssa Ross <hi@alyssa.is>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH optional] linux: use 6.18 for generic images
Date: Thu, 02 Jul 2026 23:20:04 +0000	[thread overview]
Message-ID: <pdYkFEpbCulumAjJWEDuEMO1TyiIRFs102rKrnoiO6DFlpl_49VNDFbKZQMMSMeG-41OZutXrVnTYS0XVEwb8mOHKPKn8Px6ckVFYDOv6Qc=@colbyt.com> (raw)
In-Reply-To: <87bjcpwlse.fsf@alyssa.is>

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 update and going to the newest kernel.  

All of those sets are just all the things I had to do to get to nixlatest and boot native apple devices, in case you didn't have any of those update patches on your local.



On Thursday, July 2nd, 2026 at 7:28 AM, Alyssa Ross <hi@alyssa.is> wrote:

> colbyt <colby@colbyt.com> writes:
> 
> > Keep the generic rootfs, app VM, net VM, and installer on the linux_6_18
> > package set after updating nixpkgs.
> >
> > This is an optional conservative variant for deployments that should stay
> > 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 updating
> > 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 <colby@colbyt.com>
> 
> In Spectrum proper I'd like to stick to the latest stable kernels.
> There are a few reasons for this:
> 
> • Backports, including security fixes, to older kernels are best-effort,
>   and sometimes end up getting missed.
> • 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).
> • New features from new kernels!
> 
> 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.
>

  reply	other threads:[~2026-07-02 23:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 18:55 [PATCH 0/8] refresh nixpkgs for Linux 7.1 colbyt
2026-06-26 18:55 ` [PATCH 1/8] pkgs: fix aarch64-musl builds with current nixpkgs colbyt
2026-07-02 12:18   ` Alyssa Ross
2026-06-26 18:55 ` [PATCH 2/8] lib: update nixpkgs colbyt
2026-06-26 18:55 ` [PATCH 3/8] pkgs/skaware: vendor backported patches colbyt
2026-07-02 11:53   ` Alyssa Ross
2026-06-26 18:55 ` [PATCH 4/8] pkgs/gtk3: skip integrated Wayland backport colbyt
2026-07-02 12:19   ` Alyssa Ross
2026-06-26 18:55 ` [PATCH 5/8] pkgs/skaware: skip integrated backports colbyt
2026-06-26 18:55 ` [PATCH 6/8] pkgs/cloud-hypervisor: update GPU patchset to v52 colbyt
2026-06-26 18:55 ` [PATCH 7/8] pkgs/libfyaml: fix pkg-config libs colbyt
2026-06-26 18:55 ` [PATCH 8/8] vm-lib: allow app VMs to name closure roots colbyt
2026-07-02 13:38   ` Alyssa Ross
2026-07-02 23:40     ` colby
2026-07-03 14:02       ` Alyssa Ross
2026-06-26 18:55 ` [PATCH optional] linux: use 6.18 for generic images colbyt
2026-07-02 13:42   ` Alyssa Ross
2026-07-02 23:20     ` colby [this message]
2026-07-02 12:03 ` [PATCH 0/8] refresh nixpkgs for Linux 7.1 Alyssa Ross

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='pdYkFEpbCulumAjJWEDuEMO1TyiIRFs102rKrnoiO6DFlpl_49VNDFbKZQMMSMeG-41OZutXrVnTYS0XVEwb8mOHKPKn8Px6ckVFYDOv6Qc=@colbyt.com' \
    --to=colby@colbyt.com \
    --cc=devel@spectrum-os.org \
    --cc=hi@alyssa.is \
    /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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).