The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: Gert-Jan Rodenburg <hertog@home.nl>,
	Jonathan Morton <chromi@cyberspace.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Defaulting new questions in scripts/Configure?
Date: Thu, 25 Oct 2001 14:09:55 +0100	[thread overview]
Message-ID: <20011025140955.A4942@vnl.com> (raw)
In-Reply-To: <20011025032741.K24348@vnl.com> <20011025105921.GNXL27467.mail2.home.nl@there>
In-Reply-To: <20011025105921.GNXL27467.mail2.home.nl@there>

On Thu, Oct 25, 2001 at 12:59:22PM +0200, Gert-Jan Rodenburg wrote:
> On Thursday 25 October 2001 04:27, Dale Amon wrote:
> > I've just skimmed through the code in Configure to
> > see if there is a way to make it shut up and just
> > default everything new to NO so I can use it inside
> > a noninteractive script.
> >
> > Did I miss it or is it something that isn't there
> > to be found?
> >
> > I think I'd not be the only one to find it useful
> > to make it be seen and not heard during a
> > make oldconfig :-)
> 
> 
> no "" | make oldconfig
> 
> Not sure if it works, but in the Linux From Scratch manual they do the 
> oposite ->  yes "" | make config
> 

Jonathan Morton suggested the yes is the answer
as well. I tested both out and diffed against one
done manually. no seems to just die, yes does just
the right thing.

Thanks much to all who replied.

-- 
------------------------------------------------------
Use Linux: A computer        Dale Amon, CEO/MD
is a terrible thing          Village Networking Ltd
to waste.                    Belfast, Northern Ireland
------------------------------------------------------

  parent reply	other threads:[~2001-10-25 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25  2:27 Defaulting new questions in scripts/Configure? Dale Amon
2001-10-25  2:43 ` Alexander Viro
     [not found] ` <20011025105921.GNXL27467.mail2.home.nl@there>
2001-10-25 13:09   ` Dale Amon [this message]
2001-10-25 13:44     ` Gert-Jan Rodenburg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011025140955.A4942@vnl.com \
    --to=amon@vnl.com \
    --cc=chromi@cyberspace.org \
    --cc=hertog@home.nl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox