Date: Thu, 12 May 2005 14:33:25 -0400
To: jmerkey <jmerkey@utah-nac.org>
Cc: Scott Robert Ladd <lkml@coyotegulch.com>, linux-kernel@vger.kernel.org
Subject: Re: Automatic .config generation
Message-ID: <20050512183325.GA23621@csclub.uwaterloo.ca>
References: <42839AF7.4030708@coyotegulch.com> <42838D4C.3040207@utah-nac.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42838D4C.3040207@utah-nac.org>
User-Agent: Mutt/1.3.28i
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 735
Lines: 20

On Thu, May 12, 2005 at 11:07:24AM -0600, jmerkey wrote:
> Scott Robert Ladd wrote:
> >Is there a utility that creates a .config based on analysis of the
> >target system?
> 
> Now that's a great idea ..... :-) 

And how would it guess if you want iptables support enabled or not?
Which device drivers to include is not the only thing that goes in
.config after all.

A simpler solution is turn on everything as modules, and let
hotplug/discover figure it out at boot time. :)

Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/