From owner-freebsd-arch@FreeBSD.ORG Sun Jun 12 18:50:39 2011 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11DF3106566C for ; Sun, 12 Jun 2011 18:50:39 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) by mx1.freebsd.org (Postfix) with ESMTP id 968CF8FC0C for ; Sun, 12 Jun 2011 18:50:38 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 4B73525D3893; Sun, 12 Jun 2011 18:50:37 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 5D9E615A182D; Sun, 12 Jun 2011 18:50:36 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 81q0skfIZqmC; Sun, 12 Jun 2011 18:50:35 +0000 (UTC) Received: from orange-en1.sbone.de (orange-en1.sbone.de [IPv6:fde9:577b:c1a9:31:cabc:c8ff:fecf:e8e3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 3918F15A1819; Sun, 12 Jun 2011 18:50:34 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Bjoern A. Zeeb" In-Reply-To: Date: Sun, 12 Jun 2011 18:50:34 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Warner Losh X-Mailer: Apple Mail (2.1084) Cc: freebsd-arch@FreeBSD.org Subject: Re: [RFC] shipping kernels with default modules? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2011 18:50:39 -0000 On Jun 12, 2011, at 5:51 PM, Warner Losh wrote: >=20 > On Jun 12, 2011, at 12:36 AM, Adrian Chadd wrote: >=20 >> On 11 June 2011 17:21, Adrian Chadd wrote: >>=20 >>> 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? >>=20 >> The immediate problem - how does one get the config parameters from >> the kernel configuration file to appear in the per-module build = setup? >=20 > For options, we've been doing that for years. Config generates the = opt_foo.h files, and they are picked up by the modules. >=20 >> Or, in a more general sense, how do you do per-module configuration? >=20 > 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? --=20 Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family.