From owner-freebsd-current@FreeBSD.ORG Thu Aug 14 08:47:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5282037B401; Thu, 14 Aug 2003 08:47:24 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41F7543FB1; Thu, 14 Aug 2003 08:47:23 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h7EFl2nq004654 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 14 Aug 2003 11:47:02 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h7EFkvF02091; Thu, 14 Aug 2003 11:46:57 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16187.44785.91962.402945@grasshopper.cs.duke.edu> Date: Thu, 14 Aug 2003 11:46:57 -0400 (EDT) To: John Baldwin In-Reply-To: References: <20030814100248.GB88037@sunbay.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: Luoqi Chen cc: current@freebsd.org Subject: RE: Change to kernel+modules build approach X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2003 15:47:24 -0000 John Baldwin writes: > > On 14-Aug-2003 Ruslan Ermilov wrote: > > On Thu, Aug 14, 2003 at 02:10:19AM -0600, Scott Long wrote: > >> Luoqi Chen wrote: > > [...] > >> >On the other hand, all modules should create all the opt_*.h files > >> >it needs when built individually. Add opt_ddb.h to nullfs's Makefile > >> >should fix the breakage. > >> > > >> Our kernel build system isn't set up to handle passing config options > >> to modules. Various solutions to this have been proposed, but nothing > >> has appeared yet. In 5.x, we document that modules will not work with > >> PAE. > >> > > How does the below look? This is basically a more generic implementation > > of Luoqi's idea, but for -CURRENT: > > I would prefer something far more radical that would involve moving > all the module metadata to sys/conf (i.e. removing sys/modules) and > building all the modules based on a single kernel config file. Would this tie modules to that kernel config? If so, would it mean the end of the ability of 3rd party developers to ship binary drivers and expect them to work with any kernel? Drew