From owner-freebsd-current@FreeBSD.ORG Tue Apr 22 05:46:33 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 5668A37B401 for ; Tue, 22 Apr 2003 05:46:33 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B72243FDF for ; Tue, 22 Apr 2003 05:46:32 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h3MCkTA7031631; Tue, 22 Apr 2003 06:46:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 22 Apr 2003 06:45:48 -0600 (MDT) Message-Id: <20030422.064548.89803373.imp@bsdimp.com> To: dcs@tcoip.com.br From: "M. Warner Losh" In-Reply-To: <3EA531A0.3060209@tcoip.com.br> References: <3E9EB7DF.4040104@tcoip.com.br> <20030417.205459.78025666.imp@bsdimp.com> <3EA531A0.3060209@tcoip.com.br> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Auto kernel module loading 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: Tue, 22 Apr 2003 12:46:33 -0000 In message: <3EA531A0.3060209@tcoip.com.br> "Daniel C. Sobral" writes: : M. Warner Losh wrote: : > In message: <3E9EB7DF.4040104@tcoip.com.br> : > "Daniel C. Sobral" writes: : > : Plan once was for loader to identify the PNP IDs and load the : > : appropriate modules. What the appropriate modules were would be infered : > : from a configuration file. : > : : > : I think Mike decided that wasn't such a good idea after all, but I : > : wasn't much in touch with FreeBSD at the time, so I remember it only : > : vaguely. : > : > Yes. My plan is to make devd deal with most of the problem... You'll : > still need to compile / device into your kernel, however. : : Mmmm? The point is having a minimal kernel.ko. If you still have to : compile the device in the kernel, it does nothing at all to reach the : desired goal. You misunderstand. I have a fairly minimal kernel.ko. You have to compile "/ device" into your kernel means that you have to compile the device that you get your "/" partition from. Sorry if that didn't parse. Right now I have kinda gross things like the following in my devd.conf file: nomatch 10 { match "bus" "cardbus[0-9]+"; match "vendor" "0x10b7"; match "device" "0x5257"; action "kldload if_xl"; }; nomatch 10 { match "bus" "pccard[0-9]+"; match "manufacturer" "0x015f"; match "product" "0x000a"; action "kldload if_an"; }; I've just gotten this working with devd, so I've not had a chance to optimize things completely at this point in time. However, the above entries have allowed me to compile a minimal kernel.ko and have the devices loaded on demand. I don't bother trying to unload them on last use, however, since that is a big pita... Warner