oh I know, that's why I put Bazzite on a different physical drive so I can just remove it while inst
oh I know, that's why I put Bazzite on a different physical drive so I can just remove it while installing Windows if I need to
Osame difference
Owindows doesnt care
Aeven if it was you cant the people that make these choices dont actually run distros
Dits no where close actually, all i can find is some redhat employee running an investigation on fedora coreos
Dwill be a long while i take it before it goes beyond that
Aif we didnt push them they wouldnt have implemented a loading bar still
OThe moment VR starts to actually work I can delete Windows entirely. Something to look forward to.
Din general though, a uki bundles in the cmdline, it would require a fundamental change to how things currently work in bazzite, we wouldn't need grub anymore since efibootmgr would be in charge of registering ukis with efi boot entries
Dso on update, when everything is generated, the uki blob gets created, and then registered with efi, but again, would require a substantial and fundamental change, nothing at all with how bazzite updates work atm
Aim pretty sure the proposal uses systemd boot
Awhich is a UKI manager
R
Ausers cant be expected to manage their UEFI settings that ship has sailed
RWhat does this guy mean?
RBazzite doesn't have beta stuff
WI think I used this one last time Windows had files it couldn't move when I needed to shrink the partition https://www.easeus.com/partition-manager/epm-free.html
Aand I use UKI btw
Dperhaps, though is systemd-boot really that bad? i find it rocksolid compared to grub
Dyou're not on bazzite?
Amost of my users are on bazzite, I dont daily it yet
Wprobably talking about the bazzite testing branch?
Ai didnt say systemd boot is bad, my focus was more on using the BIOS
Doh i see, what do you use? arch?
Ayeah
Di see
AUKIs work fine and boot faster, but bios updates can wipe their entries
Aand users cant conceptualize it, and there can be bugs
Aso targetting a bootloader is better for now
Aas for systemd boot and grub, they're equally meh imo
RAccording to Kyle, those are still stable packages
Dmakes sense, the link i shared earlier did make mention what they're doing is just a proposal at this stage
RSo I guess the guy in the comment must have confused things
Dits unclear if they're even working on it
Athe problem imo is that systemd boot and grub are not accessibility friendly
Drpm-ostree github page is talking about how all dev work is on bootc/dnf, they're only fixing bugs for rpm-ostree
Athey dont support touchscreens, controllers, volume buttons etc. Some of the limitation is due to their implementation
Di get the impression this is just until fedora 41 drops
AI would personally use refind for a for a user facing mobile distro. But refind has other issues
Asuch as not respecting /boot/loader entries
Orefind was the bootloader I picked when I tried to install Arch
Oit didn't go well
Obut in its defense, I was a dumbass and did dumb things with it
Olucky for me I know how to recreate a Windows boot partition <_<;;
Di remember trying to make refind work with endeavouros, got as far as making a hook so that on kernel upgrades i can generate a boot stanza, i ended up abandoning it and hiding systemd-boot behind plymouth lol
Ayeah refind is more of a install it so you can dual boot, i dont think theres any distro shipping it
Ryall dual boot?
Rwindows and linux?
WI have windows on another drive on this machine but considering nuking it lol
Hyes
AI likely would myself but I disagree with windows 10+ ToS so I can't use it at all