From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 18 01:15:01 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id CDAAF1065670 for ; Sat, 18 Feb 2012 01:15:01 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-150-251.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 79086153114; Sat, 18 Feb 2012 01:14:24 +0000 (UTC) Message-ID: <4F3EFB70.5000102@FreeBSD.org> Date: Fri, 17 Feb 2012 17:14:24 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.1) Gecko/20120213 Thunderbird/10.0.1 MIME-Version: 1.0 To: matt References: <4F3E8225.9030501@FreeBSD.org> <4F3E8C26.3080900@FreeBSD.org> <4F3EA5F2.9070804@gmail.com> <4F3EAE5F.6070903@gmail.com> <20120217.220802.988.2@DOMY-PC> <4F3EDEBC.7040703@gmail.com> In-Reply-To: <4F3EDEBC.7040703@gmail.com> X-Enigmail-Version: 1.3.5 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: rank1seeker@gmail.com, hackers@freebsd.org Subject: Re: 8 to 9: Kernel modularization -- did it change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Feb 2012 01:15:01 -0000 On 02/17/2012 15:11, matt wrote: > We have a modular kernel. It makes best-practices-sense to keep the > kernel true to what's required to boot and initialize the hardware > required to come up multiuser. I am actually against having sound in > there at all. I think the question is not, "What should be in the kernel?" but rather "What should be on by default?" *How* those things are provided is a different question. One could argue that an intelligent installer combined with a more modular kernel would be the right answer. > However, as a compromise, if it must be in there, then put it in > loader.conf and not the kernel. I keep hoping that if I repeat this enough times that people will get the word. :) Because loading modules through loader.conf is veeeeeerrrrryyyyyy sssssllllloooooowwwwww I added an rc.d script called kld that will load the specified modules after disks are mounted. This is at least an order of magnitude faster. Look for kld_list in rc.conf(5) if you want the details, but the short version is that you just do something like, kld_list="umass coretemp ichwd linux nvidia". This is in all the -stable branches (including 7), is already in 9.0, and will be in 8.3. Obviously you have to have everything in kernel and/or loader.conf that's necessary to get your local disks available, and the system to the point where it can start running rc. But everything else can go in kld_list. hth, Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/