From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 18:23:21 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D494B16A404 for ; Mon, 25 Feb 2008 18:23:21 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id B0DB113C4DB for ; Mon, 25 Feb 2008 18:23:21 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m1PHiBqR081957; Mon, 25 Feb 2008 09:44:11 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.1/Submit) id m1PHiBZ9081956; Mon, 25 Feb 2008 09:44:11 -0800 (PST) (envelope-from obrien) Date: Mon, 25 Feb 2008 09:44:11 -0800 From: "David O'Brien" To: Adrian Chadd Message-ID: <20080225174410.GA81874@dragon.NUXI.org> Mail-Followup-To: freebsd-hackers@freebsd.org, Adrian Chadd , hackers@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: hackers@freebsd.org Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 18:23:21 -0000 On Sun, Feb 24, 2008 at 07:26:04PM +0900, Adrian Chadd wrote: > I was just wondering why we're not shipping a GENERIC type > configuration that simply loads the modules at startup, rather than a > statically linked kernel. I thought that was a large part of the push > for the modular framework in years past. .. > http://people.freebsd.org/~adrian/loader.conf As you've shown the magic is in the loader.conf. I don't know a good way to handle this other than attempt to load every module (like Microsoft NT installer does) - and hope the probe of a driver that doesn't claim a device doesn't leave that device in a bad state. Have you tried putting every module in /boot/kernel into loader.conf in a "load" statement? -- -- David (obrien@FreeBSD.org)