I don't know. If they are not that is something that can/should be added
I don't know. If they are not that is something that can/should be added
GIt depends on how big /boot is right?
MUKIs will go into /boot/EFI unless uefi driver is shipped for ext4
MWait. You will still need the pair data which would need to be done on local system so might as well not include bt driver at build time
GAh
GYeah Bluetooth is tricky
GSo a UKI with all of the decryption modules + nvidia is around 200mb?
MYes. Maybe a bit more. And remember that fat32 you lose space
GWell
GUKIs hopefully will make secureboot actually secure and make systems more reliable, seems like a decent tradeoff to me. Maybe by the time they ship UKIs for Silverblue, NVK will be rock solid compared to the proprietary nvidia driver in performance
Abut boot is not efi
Aunless you do one combined partition, it doesnt make sense to use /boot/EFI
Aaccording to the spec they will go to /boot/Linux
GAh that's a bit more space
MBut boot is ext4 right now which uefi doesn't have a driver for by default
Aif we're using a combined partition, users will have to reinstall, so it can be say 4gb
GLooks like /boot has 1gb vs /boot/EFI being 600mb
AEFI uppercase is the dir inside the efi partition
Athat the UEFI looks into
Aso /boot/efi
MYes. And that's FAT32
Athen /boot/efi/EFI is where the efis go
Aor /efi that i think is recommended now
MYepp.
M/efi/EFI/Linux/*.efi
WWhy 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
