Date: Tue, 9 Feb 2021 09:53:27 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: Michael Schuster <michaelsprivate@gmail.com>, "Oleg V. Nauman" <oleg@theweb.org.ua> Cc: freeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: "make" in ports tells me "requires kernel source files in SRC_BASE=/usr/src." despite an up-to-date /usr/src Message-ID: <a71737ff-39f6-21ec-a4aa-a542aa70ce49@FreeBSD.org> In-Reply-To: <CADqw_gL=9hY77i%2BnG6YCsVEFEzce0PngfrY9U_RYC2rrwD1MeQ@mail.gmail.com> References: <CADqw_gKG6ovTuN7bZvYy7PCydfCXH4M2fw68YLmLvZhxi-g2xw@mail.gmail.com> <601d6f51-e3e5-a780-332a-95648fe87168@yuripv.dev> <2281312.bDOn7JOVgO@sigill.theweb.org.ua> <CADqw_gL=9hY77i%2BnG6YCsVEFEzce0PngfrY9U_RYC2rrwD1MeQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/02/2021 20:10, Michael Schuster wrote: > $ bectl list > BE Active Mountpoint Space Created > [...] > BE_20210206_175312_CURRENT14 NR / 30.8G 2021-02-06 17:53 > BE_20210208_204901_CURRENT_14 - /mnt 860K 2021-02-08 20:49 > > ... which, as I found out, does NOT include /usr/src; only after creating a > snapshot of same and mounting that specifically: There's an important difference between beadm and bectl which seems relevant here. beadm defaults to accepting a tree of ZFSes as a boot environment, whereas bectl only applies to the ZFS at the top level of the boot environment unless you use the -r flag. I don't know why the difference was introduced, since bectl was specifically written as a drop-in replacement for beadm, and the recursive behaviour of beadm is generally what you'ld want if you have several ZFSes per boot environment and entirely harmless if you only have a single ZFS per BE. Cheers, Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a71737ff-39f6-21ec-a4aa-a542aa70ce49>