Date: Sun, 12 Jun 2011 18:50:34 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-arch@FreeBSD.org Subject: Re: [RFC] shipping kernels with default modules? Message-ID: <B2BF0A26-1819-49C2-8331-3F00712AF523@lists.zabbadoz.net> In-Reply-To: <BDC0C06C-3152-49AF-A0F7-86A05AF14288@bsdimp.com> References: <BANLkTin2AwKRT7N6HWqBctJcT72_mR=Otg@mail.gmail.com> <BANLkTinJP%2BmSiacOO03r8zAY_79ABDy_EQ@mail.gmail.com> <BDC0C06C-3152-49AF-A0F7-86A05AF14288@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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 ;)
> Or did you have something else in mind when you asked?
--
Bjoern A. Zeeb You have to have visions!
Stop bit received. Insert coin for new address family.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B2BF0A26-1819-49C2-8331-3F00712AF523>