Date: Wed, 16 Dec 2020 10:31:01 -0500 From: Ryan Moeller <freqlabs@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: (239489) buildkernel fails if PORTS_MODULES= includes openzfs-kmod Message-ID: <f35a527c-2cd0-b2cc-1df5-424aa3ac28a4@FreeBSD.org> In-Reply-To: <X9ZOdSDF7uuGRizQ@phouka1.phouka.net> References: <7fe2fe36-a342-e863-a63e-47f6890f8220@gmail.com> <X9ZOdSDF7uuGRizQ@phouka1.phouka.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/13/20 12:25 PM, John Kennedy wrote: > On Sun, Dec 13, 2020 at 08:19:30AM +0000, Graham Perrin wrote: >> Please: is there some way to include openzfs-kmod at buildkernel time? Not that I'm aware of, but you can write a script to build your system the way you like it and then build the kmod, clone a BE, etc, so you don't forget anything. >> To work around >> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239489> I habitually >> remove openzfs-kmod from /etc/src.conf _and_ modify /boot/loader.conf >> before performing the build: >> >> zfs_load="YES" >> openzfs_load="NO" > Isn't openzfs-kmod on 13-CURRENT more or less moot since r36474, the OpenZFS > merge, ~2020/8/25? That ticket was opened on 2019/7/28, pre-merge. The port tracks the openzfs/zfs master branch while the base system tracks the zfs-2.0-release branch. However, that is planned to switch to master once base makes the transition to git. > Now, I still see recent updates on openzfs-kmod port so the question might > still be relevant for non-13 or if you're just using the port for reasons or > anywhere older than 13 (12.2, etc). If the newer features in master (eg draid) aren't needed, the base zfs is at least less likely to break from kernel changes that haven't been coordinated well with the openzfs upstream and the port, which does happen from time to time. -Ryan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f35a527c-2cd0-b2cc-1df5-424aa3ac28a4>