Date: Mon, 25 Oct 2004 12:43:37 -0600 (MDT) From: "Ryan Sommers" <ryans@gamersimpact.com> To: "Andre Guibert de Bruet" <andy@siliconlandmark.com> Cc: current@freebsd.org Subject: Re: Breaking up kernel config files (GENERIC) 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> <p06110423bd9f1b6312ed@[128.113.24.47]> <41796D6D.7000108@freebsd.org> <41799315.70201@elischer.org> <41799396.9090307@freebsd.org> <20041023082926.GE45235@ip.net.ua> <p06110433bda0a9094720@[128.113.24.47]> <p0611043abda24d6ecffe@[128.113.24.47]> <20041025141556.I42571@alpha.siliconlandmark.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?63488.208.4.77.15.1098729817.squirrel>