Zhenlei Huang – FreeBSD committer zlei@ – draws attention to <https://reviews.freebsd.org/D39695>, and respectfully suggests consideration of merges where three commits have been on the main branch for a few months:
<https://github.com/freebsd/freebsd-src/commit/bc0c6c9cf3a9f9a54dbdd92dd8f1f65ff8092d17>
<https://github.com/freebsd/freebsd-src/commit/d3b6d70e0dfaa4e9496bddcbc212d7d3ea392800>
<https://github.com/freebsd/freebsd-src/commit/d76ef58d566ccf203b21a1c8fea55985f355d4d2>
Respectively:
― ⚙ D39695 freebsd-update: Add check for kernel modules
― freebsd-update: Add check for kernel modules · freebsd/freebsd-src@bc0c6c9
― freebsd-update(8): Use kern.module_path · freebsd/freebsd-src@d3b6d70
― freebsd-update: Correctly check if pkg(8) is present · freebsd/freebsd-src@d76ef58
<https://lists.freebsd.org/archives/freebsd-questions/2024-November/005992.html>
「Building a ported kernel module, where the Project-provided package is inferior」
For readers with a passing interest: to the best of my knowledge, freebsd-update(8) is simply not usable – not testable – with FreeBSD-CURRENT (from the main branch) or STABLE (branches where degrees of testing occur, parallel to short-lived releng branches).
<https://wiki.bsd.cafe/docs:freebsd:choose>
#UX #review #MFC #FreeBSD #ports #ported #kmod #kernel #modules #update #upgrade