From owner-freebsd-questions@FreeBSD.ORG Thu Mar 31 22:31:50 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E99C16A4CE for ; Thu, 31 Mar 2005 22:31:50 +0000 (GMT) Received: from smtpq3.home.nl (smtpq3.home.nl [213.51.128.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06EBC43D1F for ; Thu, 31 Mar 2005 22:31:49 +0000 (GMT) (envelope-from danny@ricin.com) Received: from [213.51.128.133] (port=43618 helo=smtp2.home.nl) by smtpq3.home.nl with esmtp (Exim 4.30) id 1DH8CZ-0005fS-SB for freebsd-questions@freebsd.org; Fri, 01 Apr 2005 00:31:47 +0200 Received: from cp464173-a.dbsch1.nb.home.nl ([84.27.215.228]:56133 helo=desktop.homenet) by smtp2.home.nl with esmtp (Exim 4.30) id 1DH8CY-00026V-7t for freebsd-questions@freebsd.org; Fri, 01 Apr 2005 00:31:46 +0200 From: Danny Pansters To: FreeBSD Questions Date: Fri, 1 Apr 2005 00:31:36 +0200 User-Agent: KMail/1.8 References: <810a540e05033109433254f791@mail.gmail.com> In-Reply-To: <810a540e05033109433254f791@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504010031.36878.danny@ricin.com> X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean Subject: Re: How to find needed modules for rebuilding kernel X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 22:31:50 -0000 On Thursday 31 March 2005 19:43, Pat Maddox wrote: > In rebuilding a kernel, how do you know exactly what modules you need? > The Handbook is a good start, and a lot of them are obvious (i.e. if > I have no SCSI disks, disable all SCSI modules). Others aren't so > easy, particularly serial devices, and the pseudo devices. How can I > find out exactly what I need to enable, so I can make the kernel as > tight as possible? Modules are not your concern, they get built anyway (or mostly .. not sure but probably not each and every possible module gets built). The idea is that if you for example need support for a new soundcard, you can just load the module (loader.conf) without needing to recompile the kernel. On an IDE/ATA system I generally turn down the scsi delay (I always do) and remove: - all scsi raid cards and support - all ethernet cards, both pci/isa and usb except the one(s) I have (most can be loaded as a module also); beware whether it needs mii too - from the pseudo devices ppp/tun/slip as I'm connected via ethernet (cable) sometimes I disable ipv6 and gif/faith, sometimes I don't - all CPUs except the one you actually have (performance!) I also remove most scsi support but beware that cdrecord (atapicam) requires the basic scsi devices, as does umass (camera's, cf fards, usb scanners, ..). Generally unless you need to _add_ something to your kernel you don't really need to stray from GENERIC at all. If you want to have a kernel at least tuned for your CPU and without a lot of stuff you don't have anyway, do the above). But depending on the purpose of the box you can strip out quite a lot. Check NOTES, both in /usr/src/sys/conf and /usr/src/sys//conf. (on FreeBSD4 that is LINT). Also most if not all drivers and devices have manual pages and from the synopsis you can see which other devices or options come with them. HTH, Dan