From owner-freebsd-current@FreeBSD.ORG Mon Oct 25 18:46:18 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 26CC016A4CE for ; Mon, 25 Oct 2004 18:46:18 +0000 (GMT) Received: from mailserv1.neuroflux.com (mailserv1.neuroflux.com [204.228.228.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA02A43D46 for ; Mon, 25 Oct 2004 18:46:17 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 67569 invoked by uid 89); 25 Oct 2004 18:43:37 -0000 Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1) by localhost with SMTP; 25 Oct 2004 18:43:37 -0000 Received: from 208.4.77.15 (SquirrelMail authenticated user ryans@gamersimpact.com); by www2.neuroflux.com with HTTP; Mon, 25 Oct 2004 12:43:37 -0600 (MDT) Message-ID: <63488.208.4.77.15.1098729817.squirrel@208.4.77.15> In-Reply-To: <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> <20041025141556.I42571@alpha.siliconlandmark.com> Date: Mon, 25 Oct 2004 12:43:37 -0600 (MDT) From: "Ryan Sommers" To: "Andre Guibert de Bruet" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: Garance A Drosihn 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:46:18 -0000 Andre Guibert de Bruet said: > 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. I've thought about something like this. I'm sure some of us use our own "semi-automated" generation method of just doing something like dmesg | awk '{print $1}' | sed 's/:.*$//' | sort -u. I generally do something like this anytime I'm given a box and told to assimilate it to FreeBSD. I just take the output of this and use it as a base for what modifications I have to do to GENERIC. I'm sure someone could whip up a sed/awk script to do something like this pretty easily. A more complicated approach would involve actual hardware probing, generating dependency trees, compile time optimizations, etc. -- Ryan Sommers ryans@gamersimpact.com