J
JThis is where I'm at right now. 
Jbut a stable channel with an fsync kernel would let us drop asus and surface images
MOnly surface
Joh what's the tldr on asus?
M@Kyle Gospo but I'm tracking that the Asus kernel is still needed for ROG devices
Kfsync has the full ROG patch set
Kwe don't bother with it in bazzite at all
MOh
MThen yeah. We drop all our builds down to main/nvidia
JSo for Bluefin this is effectively "run bazzite's old kernel at a pace dictated by coreOS"
MYes
Jok that makes sense
Jso, from a product perspective
Jwe have GTS, the minivan, which will be on a gated kernel and fedora -1
Jwe have latest which is basically for the people who want the latest, no gates - IMO we keep this opt-in, the cool kids know how to get it.
Jand then Stable becomes the sports car version of bluefin, hangs out and smokes with bazzite, probably has better grades, that kinda thing. One singular image for people who want GNOME/KDE without the dad-linux vibes of GTS.
JThat sound right?
Jso gts and latest stay on distro kernels
Jthoughts on this?
Jalso let's just call it a gated or cadenced kernel, when we say coreOS kernel I think it's confusing people to think that it's a different kernel
MWell for GTS I would still like the gated kernel
MGTS/stable will be our products. Latest merely exists as our upstream
MAnd to say that we release fedora versions on time
Jagreed, we just still have to announce that, but that seems like a nobrainer decision - I think it's more to not surprise people, we could do that in a rollup release or something.
MYeah
Jyeah latest is our dev machines, my work machines aren't on latest, seems to make sense
MI mean I've been on latest.... But yeah I'm on stable immediately
MSo a possible method to implement this without additional work from jan.
Create another caching layer for the fsync kernel.
Each day it downloads the current version of the copr. Copies to a scratch container like we do for akmods. And then tag the container with the kernel version of the rpms.
We then install the kernel with a COPY --from= like our akmods.
We run this for a month of so. Then when the coreOS kernel has caught up to current version we can start installing from there instead of koji.
what's horrible about this idea @Kyle Gospo
Create another caching layer for the fsync kernel.
Each day it downloads the current version of the copr. Copies to a scratch container like we do for akmods. And then tag the container with the kernel version of the rpms.
We then install the kernel with a COPY --from= like our akmods.
We run this for a month of so. Then when the coreOS kernel has caught up to current version we can start installing from there instead of koji.
what's horrible about this idea @Kyle Gospo
Knothing at all, I wanted to do this
Mas in implementation any footguns?
KI mean this is what our akmods are, techniclly
KI'm all for it
Mokay
Malright, if I get some time I'll setup a repository for this
Jok so we just basically keep a container as a kernel archive?
MYeah
Jthat sounds like a great idea to me
JI think we wanted to do this with steam too, but whatever
MI don't know if this will help with steam.
MI think we want a base gnome/kde image with steam installed
Jnoel wanted to have steam just be a layer you can FROM from because it needs all this janky 32 bit stuff and when it breaks bazzite can't build
Jand it would let people with custom images add steam without dealing with all that
Jbut that one's a backlog/dream right now anyway
MWell this will work only if we get started on this since the switchover will take over a month
Jthis sounds good to me, it's basically "bluefin uses older bazzite kernels"
MJOH NO HERE IT COMES
MGitHub
A caching layer for the fsync kernel from sentry/kernel-fsync - ublue-os/fsync
MInitial implementation in place
