[systemd-devel] why does bootctl default to /boot and not to /boot/efi?
Lennart Poettering
lennart at poettering.net
Mon May 30 16:49:12 UTC 2016
On Mon, 30.05.16 10:51, Simon McVittie (simon.mcvittie at collabora.co.uk) wrote:
> On 29/05/16 19:39, Barry Scott wrote:
> > I just came across the bootctl command. Atleast on Fedora 23 and 24
> > it errors out because /boot is not FAT EFI. I thought that if you are EFI
> > then the EFI was always in /boot/efi.
>
> I think mounting the EFI System Partition on /boot/efi is likely to be
> very common in practice. The kernel images in /boot are managed by dpkg
> on Debian derivatives, and dpkg requires (or at least strongly
> recommends) a POSIX filesystem on the directories it manages, so that it
> can do standard POSIX filesystem robustness tricks like hard links and
> atomic-overwrite.
On Fedora kernels are generally stored in /usr/lib/ (next to the
kmods) and copied over to /boot at install time, so that package
managers only own the kernels in /usr/lib and leave their dirty
fingers out of /boot.
Lennart
--
Lennart Poettering, Red Hat
More information about the systemd-devel
mailing list