45 Replies
This is where I'm at right now. 😄
but a stable channel with an fsync kernel would let us drop asus and surface images
Only surface
oh what's the tldr on asus?
@Kyle Gospo but I'm tracking that the Asus kernel is still needed for ROG devices
fsync has the full ROG patch set
we don't bother with it in bazzite at all
Oh
Then yeah. We drop all our builds down to main/nvidia
So for Bluefin this is effectively "run bazzite's old kernel at a pace dictated by coreOS"
Yes
ok that makes sense
so, from a product perspective
we have GTS, the minivan, which will be on a gated kernel and fedora -1
we 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.
and 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.
That sound right?
so gts and latest stay on distro kernels
thoughts on this?
also 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
Well for GTS I would still like the gated kernel
GTS/stable will be our products. Latest merely exists as our upstream
And to say that we release fedora versions on time
agreed, 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.
Yeah
yeah latest is our dev machines, my work machines aren't on latest, seems to make sense
I mean I've been on latest.... But yeah I'm on stable immediately
So 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
nothing at all, I wanted to do this
as in implementation any footguns?
I mean this is what our akmods are, techniclly
I'm all for it
okay
alright, if I get some time I'll setup a repository for this
ok so we just basically keep a container as a kernel archive?
Yeah
that sounds like a great idea to me
I think we wanted to do this with steam too, but whatever
I don't know if this will help with steam.
I think we want a base gnome/kde image with steam installed
noel 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
and it would let people with custom images add steam without dealing with all that
but that one's a backlog/dream right now anyway
Well this will work only if we get started on this since the switchover will take over a month
this sounds good to me, it's basically "bluefin uses older bazzite kernels"
OH NO HERE IT COMES
GitHub
GitHub - ublue-os/fsync: A caching layer for the fsync kernel from ...
A caching layer for the fsync kernel from sentry/kernel-fsync - ublue-os/fsync
Initial implementation in place
Ok this is sick
I am beyond excited for this
some slight cleanup
Like I'll use it in bazzite day 1
we have a weird bootstrap with this where we need the akmods repo to run the fsync kernel run
Honestly since that's the case, might as well sign it
And then there's no need to do that in the images later
basically, need something to get the kernel version from. We could do it in this workflow, but akmods is already running daily
for kernel signing, we just download the rpm. So to sign them we would need to unpack the rpm and repack
Ah yeah that's fine then, skip it
Nice setup
still has some small cuts I'm cleaning up
but once we are green I'm cleaning up git history and going to bed
Second repo I setup today and a lot of the same small cuts
heh, take a nice long sleep
you're on fire lately
even kyle is like "wow, slow down"
note: kyle would never say this
Can someone setup branch protection on main?
40 is green
jan doesn't build for 39....
on it
(branch protection)
I just did it
Going to add a shorter tag version for major_minor_patch since it looks like 201 sometimes gets incremented