From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 20 15:44:11 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51FE9106564A for ; Mon, 20 Feb 2012 15:44:11 +0000 (UTC) (envelope-from papowell@astart.com) Received: from astart2.astart.com (99-111-96-109.uvs.sndgca.sbcglobal.net [99.111.96.109]) by mx1.freebsd.org (Postfix) with ESMTP id F2B7D8FC12 for ; Mon, 20 Feb 2012 15:44:10 +0000 (UTC) Received: from laptop_81.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.4/8.14.4) with ESMTP id q1KFNrEI081436 for ; Mon, 20 Feb 2012 07:23:53 -0800 (PST) (envelope-from papowell@astart.com) Message-ID: <4F426588.7090104@astart.com> Date: Mon, 20 Feb 2012 07:23:52 -0800 From: Patrick Powell Organization: Astart Technologies User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110312 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org 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> <4F3EFB70.5000102@FreeBSD.org> In-Reply-To: <4F3EFB70.5000102@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 8 to 9: Kernel modularization -- did it change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: papowell@astart.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2012 15:44:12 -0000 On 02/17/12 17:14, Doug Barton wrote: > 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 > Oooh! Ahhh! Just what I was looking for. l will extract this from 9 and put it on my system. Much better than having to edit the loader.conf and/or having to create a rc.local script. -- Patrick Powell Astart Technologies papowell@astart.com 1530 Jamacha Road, Suite X, Network and System El Cajon, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com