Date: Thu, 3 Nov 2022 19:17:37 -0700 From: Mark Millard <marklmi@yahoo.com> To: Glen Barber <gjb@FreeBSD.org>, Warner Losh <imp@bsdimp.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: RE: FreeBSD Errata Notice FreeBSD-EN-22:23.vm (and related) could possibly use a note about updating the active loader Message-ID: <97594499-BA34-4D86-AA67-615015B29AC2@yahoo.com> References: <97594499-BA34-4D86-AA67-615015B29AC2.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
FreeBSD Errata Notices <errata-notices_at_freebsd.org> wrote on Date: Tue, 01 Nov 2022 22:20:56 UTC : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > FreeBSD-EN-22:23.vm Errata = Notice > The FreeBSD = Project >=20 > Topic: Memory pages become unreclaimable > . . . > 1) To update your system via a binary patch: >=20 > Systems running a RELEASE version of FreeBSD on the amd64, i386, or > (on FreeBSD 13 and later) arm64 platforms can be updated via the > freebsd-update(8) utility: >=20 > # freebsd-update fetch > # freebsd-update install > # shutdown -r +5min "Installing errata update" > . . . A suggestion to put a copy of the potentially updated loader variant of interest in place for actual use if desired might be a good idea. As stands the binary update material gives no hint/reminder about that step. (More than the binary update sequence might be appropriate, it is just what I happened to do.) As to why, my example went like . . . # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 13.1-RELEASE from update2.freebsd.org... = done. . . . The following files will be updated as part of updating to 13.1-RELEASE-p3: /bin/freebsd-version /boot/kernel/cam.ko /boot/kernel/kernel /boot/kernel/kernel.bin /boot/kernel/zfs.ko /boot/loader.efi /boot/loader_4th.efi /boot/loader_lua.efi /boot/loader_simp.efi . . . After the install and reboot: # ls -Tld /boot/efi/EFI/BOOT/bootaa64.efi=20 -rwxr-xr-x 1 root wheel 1262604 May 12 07:56:22 2022 = /boot/efi/EFI/BOOT/bootaa64.efi # ls -Tld /boot/loader.efi=20 -r-xr-xr-x 2 root wheel 1262588 Nov 4 01:45:05 2022 /boot/loader.efi Note: My 13.1-RELEASE media is not just a dd of the full content from FreeBSD-13.1-RELEASE-arm64-aarch64-RPI.img.xz . I have a swap partition and use GPT, not MBR, for example. Still, I expect a fair variety of systems would not get automatic use of the updated loader, whatever the details of the 13.1-RELEASE installation techniques that were originally used. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?97594499-BA34-4D86-AA67-615015B29AC2>