[Bug 264499] /boot/boot1.efifat still mentioned when updating boot code

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 19 May 2025 15:46:22 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264499

Jordan Gordeev <jgopensource@proton.me> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jgopensource@proton.me

--- Comment #2 from Jordan Gordeev <jgopensource@proton.me> ---
The stale text about "boot1.efifat" is still there in the same subsection of
the Handbook as before but the subsection's number has changed to 22.3.11.

FreeBSD 13.0 shipped without "boot1.efifat" more than 4 years ago. FreeBSD 12.x
and older are no longer supported. It is high time this text gets updated.

Giving instructions on how to use a non-existing file is unhelpful and
confusing.

It is also dangerous because a user may assume that it's just a typo and what
was really meant is to use the existing file with a similar name
"/boot/boot1.efi". Writing "/boot/boot1.efi" over the EFI System Partition
would destroy the partition's file system. Note that if the partition is
mounted, the "gpart bootcode" command would fail with an "Operation not
permitted" error but if it is not mounted, there isn't any protection.

My suggestion is to replace the text about "/boot/boot1.efifat" with a
reference to the Examples section in loader.efi(8).

There are some more problems with the text in the warning box:
  1) it is not clear what undesirable situation the text warns about
  2) GPT is mentioned as an alternative to EFI but EFI is used together with
GPT partitioning on modern systems

As updating the boot code is of general interest and not performed solely when
upgrading ZFS pools, the Handbook could have a central place where the
procedures are described and subsection 22.3.11. "Upgrading a Storage Pool"
could point to it.

-- 
You are receiving this mail because:
You are the assignee for the bug.