From: Sam Ravnborg <sam@ravnborg.org>
To: SL Baur <steve@xemacs.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Andres Salomon <dilinger@queued.net>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@codemonkey.org.uk>,
Roland McGrath <roland@redhat.com>
Subject: Re: Additional kconfig targets (cloneconfig, nonint_oldconfig etc)
Date: Wed, 30 Apr 2008 22:37:34 +0200 [thread overview]
Message-ID: <20080430203734.GA9837@uranus.ravnborg.org> (raw)
In-Reply-To: <ed10ee420804301332n5fb72f3jb9bdea03aa313fad@mail.gmail.com>
On Wed, Apr 30, 2008 at 01:32:52PM -0700, SL Baur wrote:
> On 4/30/08, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > On Wed, 30 Apr 2008 03:45:57 -0700 SL Baur wrote:
>
> > > 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 know how BSD does it, but CONFIG_IKCONFIG does embed the
> > config image in the kernel. It can be extracted with
> > scripts/extract-ikconfig.
>
> No, that's not what I meant. Now that we have a means of specifying
> a configuration file by name, it would be nice if the file name could,
> for example, be appended to EXTRAVERSION. That's all it would
> take to duplicate the behavior I misdescribed.
>
>
> Eg. `make K=HPxw4300.config ...' would have "-HPxw4300" appended
> to EXTRAVERSION. Maybe this doesn't make sense any more, but it
> was once something I wanted very much.
You can just do:
echo "-HPxw4300" > localversion
Then it gets appended to the kernel version. While not automatic is
solves your need.
Sam
next prev parent reply other threads:[~2008-04-30 20:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 18:35 Additional kconfig targets (cloneconfig, nonint_oldconfig etc) Sam Ravnborg
2008-04-29 21:24 ` Andres Salomon
2008-04-30 6:35 ` Sam Ravnborg
2008-04-30 14:43 ` Jan Engelhardt
2008-04-30 10:45 ` SL Baur
2008-04-30 15:01 ` Randy Dunlap
2008-04-30 20:32 ` SL Baur
2008-04-30 20:35 ` Roland McGrath
2008-04-30 20:37 ` Sam Ravnborg [this message]
2008-04-30 14:44 ` Jan Engelhardt
2008-05-02 10:56 ` Sam Ravnborg
2008-05-01 4:40 ` Roman Zippel
2008-05-01 6:12 ` Sam Ravnborg
2008-05-03 21:49 ` Sam Ravnborg
2008-05-02 19:09 ` Sam Ravnborg
2008-05-21 20:47 ` Andres Salomon
2008-05-21 21:11 ` Dave Jones
2008-05-21 21:38 ` Andres Salomon
2008-05-22 19:06 ` Alexey Dobriyan
2008-05-21 21:47 ` Sam Ravnborg
2008-06-13 18:10 ` Andres Salomon
2008-06-13 18:14 ` Sam Ravnborg
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=20080430203734.GA9837@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davej@codemonkey.org.uk \
--cc=dilinger@queued.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=roland@redhat.com \
--cc=steve@xemacs.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