[RFC] shipping kernels with default modules?
imp at bsdimp.com
Sun Jun 12 19:40:42 UTC 2011
On Jun 12, 2011, at 12:50 PM, Bjoern A. Zeeb wrote:
> On Jun 12, 2011, at 5:51 PM, Warner Losh wrote:
>> On Jun 12, 2011, at 12:36 AM, Adrian Chadd wrote:
>>> On 11 June 2011 17:21, Adrian Chadd <adrian at freebsd.org> wrote:
>>>> Is there any reason we aren't doing this at the moment? Eg by having a
>>>> default loader modules list populated from the kernel config file?
>>> The immediate problem - how does one get the config parameters from
>>> the kernel configuration file to appear in the per-module build setup?
>> For options, we've been doing that for years. Config generates the opt_foo.h files, and they are picked up by the modules.
>>> Or, in a more general sense, how do you do per-module configuration?
>> Generally, the modules follow the global settings, since we've never tested building some network drivers with INET and some without, for example.
> What do you mean? I have been doing that for 2 or is it 3 years; you can even see which ones depend on it in sys/conf/makeLINT.mk these days ;)
Sorry, I mean we do generally build ALL of them without INET or ALL of them with INET. While some people sometimes do things like load em with INET and say cxgb without INET in the same system, in general this hasn't been widely tested.
More information about the freebsd-arch