This was copied and pasted into vi, which shows only spaces. I thought this block should be reformatted in any case, as a block display or something like that. If nothing else, I have typed over this with spaces.

I'll inquire; I don't know.

I don't see a place where comma is appropriate, but I agree that the sentence is cumbersome.

Although block cloning is a new feature, it is optional, and it is relevant that it is enabled by default. (More so to those who watch the mailing lists, but still relevant.)

This will only be true if the system was installed from a recent enough release, right?

Loader.efi does have "Updating loader.efi on the ESP" under EXAMPLES, but does not mention fstab.

We'll want to update this too.
Commit 676824f5cdf9dfdbfca38c9cfff2398345db9211

For OpenSSL I think it's fine to reference the main update from 1.1.1 rather than the most recent update that upgraded to 3.0.11. (In contrast to OpenSSH.)

PR274502

That is true since 13.0.

There's no non ascii characters here. Maybe you mean something else?

Weirdness was visible in a previous revision:

{F69441344}

If my previous comment was marked Done but then, not shown as such, it might be symptomatic of the Phabricator issue that's listed (with a link out to a screenshot) under https://wiki.freebsd.org/Phabricator#Done. I shouldn't derail this review, so if anyone would like to discuss the issue, please find me in Matrix. Thanks.

Yeah, but there will certainly be some folks upgrading systems that were first installed with a version prior to 13.0

This entire paragraph might be better placed in:

• FreeBSD 14.0-RELEASE installation information

I have a system that may be that old. efibootmgr -v doesn't show a File on the primary line. I assume that means it uses boot/bootx86.efi; @imp, is that correct? If so, I can clarify this. That system has the ESP in fstab without noauto, so it is always mounted. I'll clarify this. Looks like it will require a little rearrangement though.

There were non-ASCII characters, and some bad formatting; I fixed both.

I could have sworn I changed this; fixed in my copy now.

But it's not enabled by default; fixed.

Is there a way to link to the PR? I haven't seen that.

If the entries are 'generated' by the firmware, they are supposed to have a File element. Older firmwares do really crazy things... Including omitting the File... When that happens, you have to assume the default for removable media, which is \efi\boot\bootXXX.efi... It's often a total crap shoot on these systems.

Also to note: if your ESP is on a gmirror, the firmware will report that it's on one of the mirror underlying devices since the doesn't know about gmirror.

And the (null) will report the full unix path if the ESP is already mounted. When the ESP is mounted, sometimes the matching up code gets things wrong wrt gmirror and other geom constructs...

UEFI and the variables use DOS-style \, FreeBSD mount points and paths use /.

I see:

\EFI\boot/bootXXX.efi

I mean, this mixture in a single phrase:

\\/

Sorry if I'm misunderstanding. Find it difficult to digest in Phabricator.

Take a look at the Boot0000 output, it's copied and pasted, and shows the DOS and BSD paths for the same thing (although BSD is usually displayed in lower case).

\EFI\boot/bootXXX.efi
is my mistake. The / should be a \. It's tricky to see...
Good Eye Graham.