[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed10ee420804300345r5d4566d2uff5c3f49f1c15107@mail.gmail.com>
Date: Wed, 30 Apr 2008 03:45:57 -0700
From: "SL Baur" <steve@...acs.org>
To: "Andres Salomon" <dilinger@...ued.net>
Cc: "Sam Ravnborg" <sam@...nborg.org>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
"Dave Jones" <davej@...emonkey.org.uk>,
"Roland McGrath" <roland@...hat.com>
Subject: Re: Additional kconfig targets (cloneconfig, nonint_oldconfig etc)
On 4/29/08, Andres Salomon <dilinger@...ued.net> wrote:
> On Tue, 29 Apr 2008 20:35:31 +0200
> Sam Ravnborg <sam@...nborg.org> wrote:
> > And we add support for a new 'commandline' parameter
> > 'K' so I can say:
> >
> > make K=/proc/config.gz defconfig
> > make K=i386_defconfig defconfig
> > make K=i386_defconfig oldconfig
> > make K=/proc/config.gz newconfig
> >
> > So K is used to specify what config file we use
> > to start out from.
I like this idea a lot. I didn't like the hardcoded `.config' 13
years ago and I still
don't like it now.
> Sounds good, I highly prefer specifying the config via env variable
> rather than embedded in the target (ie, 'make olpc_defconfig').
Is there any reasonable way to embed the configuration file name in the kernel
image like BSD does it? /proc/config.gz is a good way to retrieve way to
retrieve configuration information on a running system, not so good for pushing
kernels out to a network and keeping track of the config files on the build
machine.
I don't have any way of checking this now, but can /proc files like
/proc/config.gz
be exported via NFS or the equivalent?
-sb
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists