Date: Thu, 12 Jan 2006 00:26:09 +0100 (CET)
From: Roman Zippel <zippel@linux-m68k.org>
To: Ben Collins <ben.collins@ubuntu.com>
cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 15/15] kconf: Check for eof from input stream.
In-Reply-To: <1136814126.1043.36.camel@grayson>
Message-ID: <Pine.LNX.4.61.0601120019430.30994@scrub.home>
References: <0ISL003ZI97GCY@a34-mta01.direcway.com> <200601090109.06051.zippel@linux-m68k.org>
 <1136779153.1043.26.camel@grayson> <200601091232.56348.zippel@linux-m68k.org>
 <1136814126.1043.36.camel@grayson>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1026
Lines: 31

Hi,

On Mon, 9 Jan 2006, Ben Collins wrote:

> > That just means Debian's automatic build for the kernel has been broken for 
> > years. All normal config targets require user input and no input equals 
> > default input. Only silentoldconfig will abort if input is not available.
> 
> I think that's broken (because I don't see where that behavior is
> described).

I'll accept a patch to fix the documentation.

> IMO, based on the code, it should only go with defaults when
> -n -y or -m is passed.

No.

> Why is it so hard to error when stdin is closed? It's not like that will
> break anything.

oldconfig & co are interactive targets, so don't use them in automatic 
builds. If you some problem with using silentoldconfig, describe it and 
I'll help to solve it.

bye, Roman
-
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/