From owner-freebsd-current@FreeBSD.ORG Mon Oct 25 18:23:06 2004 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 0AAD916A4CE for ; Mon, 25 Oct 2004 18:23:06 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA81F43D2F for ; Mon, 25 Oct 2004 18:23:05 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i9PIN3Pa051616; Mon, 25 Oct 2004 14:23:03 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i9PIN3eF051613; Mon, 25 Oct 2004 14:23:03 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Mon, 25 Oct 2004 14:23:03 -0400 (EDT) From: Andre Guibert de Bruet To: Garance A Drosihn In-Reply-To: Message-ID: <20041025141556.I42571@alpha.siliconlandmark.com> References: <417960C2.8040007@freebsd.org> <20041022194008.GA23778@odin.ac.hmc.edu> <41796D6D.7000108@freebsd.org> <41799315.70201@elischer.org> <41799396.9090307@freebsd.org> <20041023082926.GE45235@ip.net.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: Breaking up kernel config files (GENERIC) 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: Mon, 25 Oct 2004 18:23:06 -0000 On Mon, 25 Oct 2004, Garance A Drosihn wrote: > At 2:24 AM -0400 10/25/04, Andre Guibert de Bruet wrote: > > So, I would expect "categories" to only handle simple cases like that, > and we would leave the lines for things like 'da' and 'scbus' just the > way they currently are. > > Right now I'm just tossing out some ideas of what we'd really like to > see. I think that if all we do is split up all the per-architecture > GENERIC kernels into smaller files, then we will end up creating *more* > work for most people who want to create a smaller kernel config. I > suspect we can come up with something better than that. What I would really like to see is a mechanism for recognizing hardware (arch, cpu family, scsi, ide, sound, firewire and net) that is currently in the system and generating a barebones configuration file with just the results. What happens when this "auto-probing" doesn't recognize the hardware that you have? Well, what are you forced to do now? :-) Regards, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >