Breaking up kernel config files (GENERIC)

[Andre Guibert de Bruet]

On Mon, 25 Oct 2004, Ryan Sommers wrote:

> 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.

The dmesg approach works well for devices but doesn't fare too well with 
"options" unless you get into some really creative scripting. The approach 
I was thinking about would make extensive use of the hw and dev sysctl 
MIBs. I should have something that "works", tonight...

Regards,
Andy

| Andre Guibert de Bruet | Enterprise Software Consultant >
| Silicon Landmark, LLC. | http://siliconlandmark.com/    >