From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Boot and EFI partitions
Date: Wed, 6 Dec 2023 18:46:04 +0000 [thread overview]
Message-ID: <fa15fbb9-821f-49f9-998f-c4202d620cbf@youngman.org.uk> (raw)
In-Reply-To: <944dd6a5-1079-41a0-8a3d-3cfaa9ec6f3c@users.sourceforge.net>
On 06/12/2023 16:36, Jack Ostroff wrote:
> The way I think of it is that the UEFI firmware needs to find the
> xxxx.efi loader, and it can only read FAT32 formatted partitions
> labelled as type esp. That xxxx.efi loader then needs to find your
> kernel and related files, but as it is specific for that type of kernel
> (linux) it can know about more partition formatting options. I suspect
> that many (most?/all?) existing linux utilities still expect the boot
> dir to be at /boot, but perhaps the docs are late to change describing
> that it no longer needs to be a separate partition, or perhaps one or
> more of those utilities still requires a partition.
It's not that far off base ... note that Macs use UEFI, but don't have
FAT32 partitions ...
On the raid wiki I say that you need *some* sort of boot partition, and
say that if you're using legacy (bios) boot you should really put /boot
on its own partition so if you decide to go UEFI, you re-purpose that
partition. It certainly seems weird that systemd-boot would want its own
partition on top of the efi partition :-)
The UEFI spec basically requires - as a minimum - that the UEFI software
in rom must be able to read fat32. There is no requirement that that is
the only format it can read, hence Macs reading the Mac format. If you
want your own boot rom that can read ext*, that's fine (so long as ext32
is also available).
Cheers,
Wol
next prev parent reply other threads:[~2023-12-06 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 15:32 [gentoo-user] Boot and EFI partitions Peter Humphreey
2023-12-06 16:36 ` Jack Ostroff
2023-12-06 18:46 ` Wols Lists [this message]
2023-12-06 16:49 ` Victor Ivanov
2023-12-06 17:34 ` Marco Rebhan
2023-12-06 18:08 ` Michael
2023-12-06 18:48 ` Victor Ivanov
2023-12-07 11:51 ` Peter Humphrey
2023-12-08 11:02 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa15fbb9-821f-49f9-998f-c4202d620cbf@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox