DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=P91Eo5+v/8vbvbwGpgoXq1Wu9ey3NZ9cO2h2bDS1ilqY65XhjjkQAn2UHmXXxtf1kaak1HpsMTIxpFpgillxejAnUDHgK46erlS/NpgBTTH/hLb9d0VBbCTJLhiJcdGXpr3p048zeeyzp7GoshBCkrVtW3BJOTJPpQwoDH5Wi3c=
Message-ID: <2cd57c9005091601112e215a1e@mail.gmail.com>
Date: Fri, 16 Sep 2005 16:11:44 +0800
From: Coywolf Qi Hunt <coywolf@gmail.com>
Reply-To: coywolf@gmail.com
To: Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com>
Subject: Re: Automatic Configuration of a Kernel
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20050914223836.53814.qmail@web51011.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <20050914223836.53814.qmail@web51011.mail.yahoo.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 791
Lines: 25

On 9/15/05, Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com> wrote:
> Hi
> 
> I wrote this Framework for making a .config based on
> the System Hardwares. It would be a great help if some
> people would give me their opinion about it.
> 
> Regards
> 
> A.R.Cheraghi
> 

How about the idea that we have a .hwconfig file and we do `make
hwconfig' to generate it? So normal filesystems and network stack
stuff don't belong to hwconfig.

.hwconfig file merely stores the result from auto hardware detection.
-- 
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
-
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/