Hello Chris, On Wed, Feb 13, 2019 at 7:49 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > I glossed over the fact upgrades to Fedora 30 will be converted to the > "bls way" of things. So I want to be sure I understand feature scope: > > - all Fedora 30 editions and spins and archs, *except* 32-bit ARM Yes, because for ARMv7 we are still booting from u-boot directly, so it needs the old grubby tool to update the extlinux.conf that's used by u-boot. There's a plan to use the u-boot uEFI stub to chain-load grub2 as it's already done for aarch64 boards AFAIK. If that's the case we could also use BLS for ARMv7. The Changes wiki page for that feature says that it's targeted for F30, but AFAIU it probably won't happen in time and we will have to keep a non-BLS configuration for ARMv7 in F30. https://fedoraproject.org/wiki/Changes/uEFIforARMv7 > - new Fedora 30 installations, and upgrades of Fedora 28 and 29 to Fedora 30 Correct. Although I would just say upgrades from F29 to F30. Or can you skip a release when doing a system upgrade? > - does not apply to install media (right now I'm seeing install media > still contains monolithic grub.conf, grub.cfg and isolinux.cfg that > have all menu entries) > Yes, I'm not that familiar with how the install media is created and its boot configuration. But I think that BLS makes less sense there since the menu entries will always be a static configuration anyways. > Thanks, > --- > Chris Murphy Best regards, Javier _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
