Why not simply enlarge `/boot/efi`?
Why not simply enlarge
/boot/efi
MSystemd-boot can load uefi drivers. And it has the concept of XBOOTLOADER so things are in place there as well.
But the most ideal thing is if /boot was just one large fat32 partition.
But the most ideal thing is if /boot was just one large fat32 partition.
MThey have. It's now 600 MB. It used to be 200 MB
Gthe Bluefin UKIs would likely be larger because of the HWE for decryption support (TPM, FIDO, etc)
Gthere would also be nvidia drivers included in some, which would make the UKIs larger
Anested mount no bueno
A/boot/efi is a partition
Aaccording to the spec, either way is fine, with a small nudge to using a single fat32 partition for boot + efi
AThe Boot Loader Specification # This document defines a set of file formats and naming conventions that allow the boot loader menu entries to be shared between multiple operating systems and boot loaders installed on one device.
Operating systems cooperatively manage boot loader menu entry directories that contain drop-in files, making multi-boo...
Operating systems cooperatively manage boot loader menu entry directories that contain drop-in files, making multi-boo...
JHuh, 6.9.4 looking green so far.
Byeah, i just came here to say... i think those betting on red owe me
Bnot that i had anything to do with it being green 
JThere's plenty left to go wrong lol
JBut you're probably right
Bmain is all green 39/40, hwe 40 is all green and i'm re-running hwe 39 misc failures
Bwhich i think was all due to a main-base 39 failure which i reran
JBazzite green as my lawn!!!
Rstill no bluefin 40 run
Rim batting on the libxml2 issue still being there
B
well, main/hwe are all green... in time for bluefin run to happen
KBazzite 3.1.0 soon???
Rsecureblue 3.0 featuring bazzite spins, soon 
R
Roh shit
Rit's fixed
R:beagle:
NIn all for this
Pwhat will be diffrent?
FGitHub
Fixes #255. Allows users to create files within /usr/lib/bootc/kargs.d with kernel arguments. These arguments can now be applied on a switch, upgrade, or edit.
General process:
use ostree commit o...
General process:
use ostree commit o...
Joh yeah!
Jexamples ^
KDoes this allow us to change kargs without a new image?
Jit let's use declare it at build time
JSeems like 6.9.X kernel broke secure boot
Rthis requires ublue to switch everything over to bootc, right?
Ris there an issue for that already
Jyeah
Kwait, where's the kargs defined now?
Krpm-ostree kargs?
Kyes
Jthere's all sorts of issues open for switching to bootc but I don't understand why we haven't merged it yet
Rfor bluefin i think there's a job that sets them after the first boot
Rjust upgraded, getting this also
Rwhy did you delete the photo lol
JGood waa trying to isolate more factors before making the final conclusion
Rit's broken
JThat seals it then 
Rshim signature invalid
R
