From owner-freebsd-questions@FreeBSD.ORG Sat Dec 19 17:41:15 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF2231065672 for ; Sat, 19 Dec 2009 17:41:15 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from mail-px0-f190.google.com (mail-px0-f190.google.com [209.85.216.190]) by mx1.freebsd.org (Postfix) with ESMTP id B84808FC08 for ; Sat, 19 Dec 2009 17:41:15 +0000 (UTC) Received: by pxi28 with SMTP id 28so2740796pxi.7 for ; Sat, 19 Dec 2009 09:41:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=pXvyE7LOEfXDjSFDQKWTYo8xPei0YFKYBty9HHvgZ/I=; b=E24pRpxZIEUn1K+Tjea3y4bGiZKJM7sLeLL42c0B18fsehYcgMKHxPNz3hp7IUTA/E XGFtG6xoJrVQsqvUpc5w2jIdQLd244VNsdPZNTWXTUwl3tA/tvx477qa0Y3mlAtmROOg BK+cTbW7M/eGnuDBYHeqelZDSGZjH8A72qsLg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ETaK9G6S9/PZuYURE+QTc6R2EDl/3iQG4sJnBbhmP7qTDMtEB6zhX76VfTAzOOACUO RD1yKoCTfj5tsTrjbxWDZ6MuFwnGIKcwsaqON9eKSIjDziGBxE1CdyK1opxPidri/NlC Sgj5URHTZ82bvfV6Z72Q6gPPBUN2WPvsmio/U= MIME-Version: 1.0 Received: by 10.115.61.16 with SMTP id o16mr3492296wak.15.1261244474875; Sat, 19 Dec 2009 09:41:14 -0800 (PST) In-Reply-To: <20091219161309.GA57855@bsdbox.koderize.com> References: <20091219161309.GA57855@bsdbox.koderize.com> Date: Sat, 19 Dec 2009 10:41:14 -0700 Message-ID: From: Tim Judd To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: question about building a custom kernel X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 17:41:15 -0000 On 12/19/09, Jamie Griffin wrote: > Hi > > I have been reading the handbook to learn about building a custom > kernel, but just wanted to ask something about gathering information > about my hardware before I give it a go. > > The handbook suggests the command: > > # pciconf -lv > > ...which I like because it provides a clear list of components I can find > out about before I try to build the new kernel. > > On my system, this command does print out information for quite a few > components, I just wondered if this information is all I need to work > from or is it not an accurate or detailed enough representation of the > hardware I have in my computer. I'd really appreciate any advice on how > others go about this. > > Jamie > Jamie, pciconf will list pci devices only (and their derivatives, like PCI-X and PCI-e). ISA devices (if any) are done differently, and also usb devices (usbdevs). Building a custom kernel most of the time involves the following decisions: embedding a firewall, so you cannot disable a firewall by unloading a module. Extending options, filesystem quotas for example. The modular kernel can add devices by modules, but can't really add options. Embedded solutions, like a single-purpose unit that is an all-in-one solution. The soekris and PC Engines firewall products come to mind. 99% of my time, I leave GENERIC (makes updating it easier with freebsd-update) alone and load the kernel modules I need. the amount of ram used with a GENERIC kernel and a "stripped" kernel to your hardware may save 2MB of disk, and 1MB of RAM. Not very worth it for the computers today where you have TB's of disk, and GB's of ram. Can I ask for more details from you why you're interested in building a custom kernel? --TJ