From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Magenheimer, Dan (HP Labs Fort Collins)" Subject: RE: (no subject) Date: Mon, 19 Sep 2005 09:57:43 -0700 Message-ID: <516F50407E01324991DD6D07B0531AD5695D44@cacexc12.americas.cpqcorp.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Content-class: urn:content-classes:message List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christian.Limpach@cl.cam.ac.uk Cc: Jerone Young , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > > > Why are you piping in tons of nothing into Make here=20 > using the "yes" > > > command? > >=20 > > This mechanically does the same as manually hitting > > "enter" at every prompt from "make oldconfig", thus it > > applies the default response for every unconfigured > > option without manual intervention. >=20 > I think it's preferable to have default config files which don't cause > any prompting. >=20 > Also if people upgrade, they probably want to be prompted on any new > options. If not, then let's get the default behaviour for "make > oldconfig" changed upstream... I've just used this for convenience. The defconfigs in Linux/ia64 cause prompting and the config change required for Xen/ia64 support (because it is transparently paravirtualized) is adding "CONFIG_XEN=3Dy". But I can easily put the output of make oldconfig in the xen defconfig file if the preference is to have no prompting (thus the "yes" pipe is removed from the previously posted patch). Thanks, Dan