-
-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
26 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2712,6 +2712,30 @@ COMMON ITEMS: | |
|
||
Non-boot pools do not need these updates. | ||
|
||
EFI notes | ||
--------- | ||
|
||
There are two locations the boot loader can be installed into. The | ||
current location (and the default) is \efi\midnightbsd\loader.efi and using | ||
efibootmgr(8) to configure it. The old location, that must be used on | ||
deficient systems that don't honor efibootmgr(8) protocols, is the | ||
fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy | ||
/boot/loader.efi to this location, but on systems installed a long time | ||
ago the ESP may be too small and /boot/boot1.efi may be needed unless | ||
the ESP has been expanded in the meantime. | ||
|
||
Recent systems will have the ESP mounted on /boot/efi, but older ones | ||
may not have it mounted at all, or mounted in a different | ||
location. Older arm SD images with MBR used /boot/msdos as the | ||
mountpoint. The ESP is a MSDOS filesystem. | ||
|
||
The EFI boot loader rarely needs to be updated. For ZFS booting, | ||
however, you must update loader.efi before you do 'zpool upgrade' the | ||
root zpool, otherwise the old loader.efi may reject the upgraded zpool | ||
since it does not automatically understand some new features. | ||
|
||
See loader.efi(8) and uefi(8) for more details. | ||
|
||
To build a kernel | ||
----------------- | ||
If you are updating from a prior version of MidnightBSD (even one just | ||
|
@@ -2830,7 +2854,7 @@ COMMON ITEMS: | |
[8] The new kernel must be able to run existing binaries used by an | ||
installworld. When upgrading across major versions, the new kernel's | ||
configuration must include the correct COMPAT_FREEBSD<n> option for | ||
existing binaries (e.g. COMPAT_FREEBSD10 to run 10.x binaries). Failure | ||
existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure | ||
to do so may leave you with a system that is hard to boot to recover. A | ||
GENERIC kernel will include suitable compatibility options to run | ||
binaries from older branches. Note that the ability to run binaries | ||
|
@@ -2853,7 +2877,7 @@ FORMAT: | |
|
||
Copyright information: | ||
|
||
Copyright 1998-2005 M. Warner Losh. All Rights Reserved. | ||
Copyright 1998-2009 M. Warner Losh <[email protected]> | ||
|
||
Redistribution, publication, translation and use, with or without | ||
modification, in full or in part, in any form or format of this | ||
|
@@ -2870,12 +2894,3 @@ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, | |
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING | ||
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE | ||
POSSIBILITY OF SUCH DAMAGE. | ||
|
||
If you find this document useful, and you want to, you may buy the | ||
author a beer. | ||
|
||
Contact Warner Losh if you have any questions about your use of | ||
this document. | ||
|
||
$FreeBSD: src/UPDATING,v 1.416.2.18 2006/02/22 11:51:57 yar Exp $ | ||
$MidnightBSD$ |