MIME-Version: 1.0
References: <8f3899df-71b7-6562-7688-7bebc6ac1f94@xwax.org>
 <D774PQ9SBXGN.2JIXM10VQVUNH@posteo.net> <37f7104c-96b0-7c19-a35a-081f879c71d6@xwax.org>
 <86509949be4dc3a8b6cf9ae6482fdd97@posteo.de> <5210eab8-eca6-67ed-dbac-668f8c0c8f00@xwax.org>
In-Reply-To: <5210eab8-eca6-67ed-dbac-668f8c0c8f00@xwax.org>
From: Liam Proven <lproven@gmail.com>
Date: Mon, 27 Jan 2025 18:47:05 +0000
Message-ID: <CAMTenCGgWOS3-syDAWemxnsA02U1hSzw4_vT75T+AKrL2vqoBw@mail.gmail.com>
Subject: Re: Solutions for EFI booting / copying kernels
To: ~alpine/users@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"

On Sun, 26 Jan 2025 at 15:17, Mark Hills <mark@xwax.org> wrote:

> What I dislike about such a proposal is VFAT lacks journaling and other
> robusness features compared to ext4, were this partition to fail a check
> on boot. That's more likely too; now that VFAT is used for a partition
> that changes on each kernel update.

I don't think this is a significant risk.

VFAT is not a filesystem in its own right: it's the name of Windows
for Workgroups' 32-bit FAT driver VXD. Linux appropriated the name for
its driver for FAT126 with Long File Names, the extension to FAT16
that was used in Windows 95 and Windows NT 3.51.

The problem is that this blurs over about 4 different types of disk format:
* Plain old DOS FAT16 with 8.3 filenames (as used in WfWg 3.11's VFAT)
* Win95 FAT16 with long file names
* Win95 OSR 2.1's FAT32, which became more common with Windows 98.
FAT32 always had LFNs.

> I can't think of a reason (pre-EFI) that VFAT has ever been required as
> /boot?

It hasn't, but the old `/boot` filesystem is not the same thing as the
EFI system partition which we're talking about here.

There have been a few reasons for a `/boot` filesystem:

* Disk over 8GB on an early EIDE machine where the BIOS can only read
from the first 8GB of the drive
* Linux setups where the root volume is not directly accessible from
the bare kernel -- for example
    - Linux with an encryped `/` filesystem
    - Linux with `/` on a filesystem that is not part of the kernel, such as ZFS
    - Linux with `/` on software RAID which must be assembled before
it can be mounted

All legit reasons but usually it would, as you say, be an ext4 or
whatever volume.

The ESP is a different consideration. For it, it is not whether the
Linux kernel can read it: it's whether the UEFI _firmware_ can read
it.

That means that in most machines it has to be a  FAT16 or FAT32
volume. exFAT is more robust but I don't think UEFI can handle it.

I have _heard_ reports of Windows-only machines with the ESP on NTFS
but it's rare.

If you want to use the ESP for the functional role of /boot, then the
systemd-boot bootloader, which is not part of system and which does
not I think _need_ systemd, does this. It is an alternative to GRUB or
Syslinux and it keeps the kernel and the initramfs in the ESP. So, you
need a bigger ESP, but it makes the bootloader much simpler.


-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lproven@cix.co.uk ~ gMail/gTalk/FB: lproven@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
IoM: (+44) 7624 227612: UK: (+44) 7939-087884
Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053