https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263322

Graham Perrin <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needs-patch
             Status|New                         |Open
                 CC|                            |[email protected],
                   |                            |[email protected]
              Flags|                            |maintainer-feedback?(imp@Fr
                   |                            |eeBSD.org)

--- Comment #1 from Graham Perrin <[email protected]> ---
Some starting points. 


<https://docs.freebsd.org/en/books/handbook/cutting-edge/#updating-bootcode>: 

* is too late in the chapter

* offers no precaution with regard to use of gpart (and damage that 
  may ensue). 


Compare with <https://www.freebsd.org/releases/13.0R/relnotes/#boot>: 

> … To update old ESP partitions, users should stop using the gpart(8) 
> utility. Instead, …

There, the paragraph continues with an architecture-specific example that
includes: 

    /boot/efi/efi/boot/bootx64.efi


loader.efi(8)
<https://www.freebsd.org/cgi/man.cgi?query=loader.efi&sektion=8&manpath=FreeBSD>
includes a more generic (XXX) mention of: 

    /efi/boot/bootXXX.efi


<https://lists.freebsd.org/archives/freebsd-current/2021-July/000331.html> –
from Warner Losh, re: 'EFI boot partition overwritten' – included memorably
neat guidance.


Elsewhere, probably in an official area, I might have seen more recent,
comparably neat guidance, which (also) takes into account the file system of
the EFI system partition _mounted by default_ (no need to use mount_msdosfs)
with more modern systems. However:

* I struggle to remember where this write-up might have been

– imp@ please, does it ring a bell, any idea where?

(I already tried searching Foundation pages, grepping doc and src …)

TIA

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

Reply via email to