On Mon, Jul 6, 2020 at 5:30 PM Samuel Sieb <sam...@sieb.net> wrote: > > On 7/6/20 4:24 PM, Adam Williamson wrote: > > If you mean the EFI boot manager entry, just renaming the existing one > > something other than "Fedora" ought to do the trick, I think. So far as > > /boot/efi goes...well, you have two choices. You can have the two > > installs share one, or have two separate ones. I *think* both options > > at least in theory ought to work, I'm not sure if anyone's tested... > > Adding another EFI partition should work, but I don't see how they could > share one. There's a single Fedora directory in there, so each install > would overwrite the files of the other. The grub.cfg can only point to > one set of boot loader entries.
And that means sharing one ESP means sharing /boot - yeah. Hmm. I'll have to test it but I'm pretty sure it's a fairly simple post-install fix to get that to work. I'm not totally certain how blscfg.mod parses /boot/loader/entries containing bls snippets with two machine IDs. Ohhhh I just thought of something. F32 and older depend on grubenv to store part of the kernel command line variables. So I think it will be necessary to do an F32 F33 side by side install for it to work. Two F32's side by side will compete over the single grubenv. -- Chris Murphy _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
