Date: Fri, 6 Jul 2018 06:17:57 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: John Baldwin <jhb@FreeBSD.org>, Konstantin Belousov <kostikbel@gmail.com> Cc: Matt Macy <mmacy@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r335916 - head/sys/conf Message-ID: <5B3EA725.4010202@grosbein.net> In-Reply-To: <2a5b1c50-0f50-bbe1-4fcd-b98f61d24571@FreeBSD.org> References: <201807032305.w63N5guY063293@repo.freebsd.org> <20180704142233.GB5562@kib.kiev.ua> <6e5bc5e4-052c-877f-1c36-c72e276ff045@FreeBSD.org> <20180705155417.GI5562@kib.kiev.ua> <2a5b1c50-0f50-bbe1-4fcd-b98f61d24571@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
06.07.2018 1:21, John Baldwin wrote: > Yes, this is a change though I find it the logical outcome of the original change > to move away from MODULES_WITH_WORLD. And to be clear, Matt certainly only > intended to use MODULE_TIED in a few places, but I think tagging all those > places will be cumbersome and tedious compared to just doing it in this way. I > think this will also tie into something I proposed earlier in a commit reply and > that I also brought up at BSDCan which is that I think that kernel modules in > ports should install their sources and build glue to some location we choose > (e.g. /usr/local/sys/modules/<foo>) and that we should support a variable folks > can set in their kernel config file similar to MODULES_OVERRIDE that is a list > of local modules to recompile and install into /boot/kernel along with other > modules (and that these recompiled modules would be TIED). The binary module > from the package would still be present in /boot/modules, but the tied module > in /boot/kernel would be preferred and used instead when it exists (our existing > module_path already does this last part). This would replace the existing > PORTS_MODULES but in a way that is more graceful and works with packages, not > just ports IMO. I'm not sure I understand the topic quite right, but please do not drop MODULES_WITH_WORLD support at it allows us to quickly rebuild the kernel in case of slight changes of its config file not changing ABI and/or similar source changes without HUGE modules compilation overhead. Also, we should not use /usr/local/sys/modules/<foo> as /usr/local can be inaccessible for the loader. Better use /boot/modules/local or /boot/local as /boot is guaranteed to be accessible.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5B3EA725.4010202>