Date: Mon, 20 Oct 2025 16:05:27 +0200 From: vermaden <vermaden@interia.pl> To: "freebsd-stable@FreeBSD.org" <freebsd-stable@FreeBSD.org>, "freebsd-pkgbase@FreeBSD.org" <freebsd-pkgbase@FreeBSD.org> Subject: Re: PKGBASE in ZFS Boot Environments World Message-ID: <vqlcgwlvwjatxocsaztu@bnlk> In-Reply-To: <nopppvhntvnlbrovskrd@yfle>
index | next in thread | previous in thread | raw e-mail
Found a way to overcome that limitation ... by creating a separate /RESCUE (not /rescue) dir with copy of /boot and pkg-static(8) command. That way one can restore /boot and reboot into different ZFS Boot Environment. Details here in the 'Additional Independent Rescue' section at the end: - https://vermaden.wordpress.com/2025/10/20/brave-new-pkgbase-world/ Regards, vermaden Temat: PKGBASE in ZFS Boot Environments World Data: 2025-10-16 10:04 Nadawca: "vermaden" <vermaden@interia.pl> Adresat: freebsd-stable@FreeBSD.org; freebsd-pkgbase@FreeBSD.org; >> We know that 'pkg delete -afy' will delete all PKGBASE >> packages without asking ... but that will also render >> ZFS Boot Environments USELESS as there is no >> loader(8) anymore to show the ZFS boot menu for BE >> selection. > > OK ls boot > boot > d zfs > d efi > loader.conf > entropy > d firmware > > My proposal - always keep a MINIMUM set of files allowing > to show loader(8) boot menu - so anyone - even after wiping > their FreeBSD system with pkg(8) - will be able to boot into > other backup ZFS Boot Environment.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqlcgwlvwjatxocsaztu>