Date: Fri, 6 Jul 2018 07:13:55 +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: <5B3EB443.50004@grosbein.net> In-Reply-To: <1dd03d43-6f0d-580b-fd3b-f4494da42c70@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> <5B3EA725.4010202@grosbein.net> <1dd03d43-6f0d-580b-fd3b-f4494da42c70@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
06.07.2018 6:59, John Baldwin wrote: >> 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. > > This would not drop it, but it would mean that you can't necessarily kldload > /boot/kernel.GENERIC/foo.ko while running some other kernel. And what's profit of such restriction? There were several cases when I was forced to extract somemodule.ko from FreeBSD distribution files and upload it to some customized installation such as FreeNAS or NAS4Free or another one running custom kernel and having stripped-down module set out-of-the-box. For example, ichwd.ko or something like that. And I was just happy I could do that and that just work. Why should we break it?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5B3EB443.50004>