On Thu, Jul 28, 2022 at 10:40 AM Lennart Poettering <mzerqung@xxxxxxxxxxx> wrote:
...
But anyway, I am actually advocating for sticking to VFAT
everywhere. ext4 drivers in the boot loader only are necessary for the
upgrade path.
I'd like to 2nd the motion to try to stick with VFAT in the boot path until real/official Linux file system drivers in the kernel/initramfs take over. Trying to maintain several parallel copies of the FS drivers in the bootloader always seemed like a bad idea to me (and a security concern as was pointed out earlier). I'm not even sure it is necessary for an upgrade path. Since the /boot partition is relatively small (even smaller if you stip out the grub stuff) and maintained by scripts anyway, it seems like it *ought* to be possible to automatically convert it or to create a new VFAT-formatted version of the partition somewhere and perhaps leave the old one as a (temporary) failback. Besides the bootloader itself, all that is really on the /boot partition is the kernel and initramfs right?
Also, this might be a little off-topic, but I've recommend that people use systemd-boot when trying to dual-boot Windows before: https://ask.fedoraproject.org/t/dual-booting-windows-10-and-fedora-34/14158/2 The user reported that they were happy with that solution later on in that thread, but one annoyance I have is that it requires setting a "SYSTEMD_RELAX_XBOOTLDR_CHECKS" variable before running "bootctl install". Is that really necessary? Why does the /boot partition require a distinct GPT type code? The /boot partition existed long before GPT and its type codes, so this seems a strange requirement (having a separate /boot was a common practice decades ago because the older BIOSes couldn't bootloaders that were placed beyond cylinder 1024 on the disk; it was also common to format /boot with FAT back then because syslinux liked to use that). I'd like to request that systemd-boot "automatically" accept/recognize a merged ESP+XBOOTLDR partition without having to set that special variable.
Thanks.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
