Updating Bootcode

Convenience? There's no specific need to have it mounted. So I've set mine to noauto. I'll mount it whenever I need to update loader.efi(8), so most of the time it's unmounted.
 
  • Like
Reactions: mer
I wonder why /boot/efi is now mounted by default.
Me too. Does anyone know?

To make "future upgrades of the EFI loader easier" in mind.

Commit "Mount the EFI system partition (ESP) on newly-installed systems."
Code:
Per hier(7), the ESP will be mounted at /boot/efi. On UFS systems,
any existing ESP will be reused and mounted there; otherwise, a new one
will be made. On ZFS systems, space for an ESP is allocated on all disks
in the root pool, but only the partition actually used to boot is set up
and mounted.

This makes future upgrades of the EFI loader easier (upgrade scripts can
just change /boot/efi) and also greatly simplifies the parts of the
installer involved in initialization of the ESP. It also makes the
installer's behavior correspond to the documentation in hier(7).
 
To make "future upgrades of the EFI loader easier" in mind.

Commit "Mount the EFI system partition (ESP) on newly-installed systems."
Code:
Per hier(7), the ESP will be mounted at /boot/efi. On UFS systems,
any existing ESP will be reused and mounted there; otherwise, a new one
will be made. On ZFS systems, space for an ESP is allocated on all disks
in the root pool, but only the partition actually used to boot is set up
and mounted.

This makes future upgrades of the EFI loader easier (upgrade scripts can
just change /boot/efi) and also greatly simplifies the parts of the
installer involved in initialization of the ESP. It also makes the
installer's behavior correspond to the documentation in hier(7).
It's well I was thinking.
 
Back
Top