On Thu, Jul 28, 2022 at 3:17 PM Lennart Poettering <mzerqung@xxxxxxxxxxx> wrote:
On Do, 28.07.22 15:03, Chris Murphy (lists@xxxxxxxxxxxxxxxxx) wrote:
> > Right. I'd like to use the ESP type code for the merged ESP+XBOOTLDR so that the firmware will pick it up properly. The only problem is when using the bootctl command to initialize that partition (/boot), it requires that I set the SYSTEMD_RELAX_XBOOTLDR_CHECKS variable. I don't think it should require setting that environment variable in that case. But maybe I'm using the command incorrectly? The command I'm running is:
> >
> > SYSTEMD_RELAX_XBOOTLDR_CHECKS=1 bootctl install --boot-path=/boot --esp-path=/boot
>
> omit --boot-path and have only an --esp-path
Correct.
I just tested omitting --boot-path and it does seem to be putting all the content under /boot. So it is my bad for misunderstanding how the bootctl parameters were supposed to be provided. Thanks!
...
One is not really supposed to have multiple ESPs on the same
medium. ...
That "on the same medium" is an interesting caveat. I've been trying to do A/B type configurations where there are two (or more) ESPs on redundant "system" drives (one per drive). I'm still not sure that it is officially supported. But it seems like it ought to be. But I guess I'm way off topic from the purpose of this thread. I look forward to Fedora Linux fixing its multiboot problems by switching to systemd-boot. :)
_______________________________________________ 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
