From: "Diego Calleja García" <diegocg@teleline.es>
To: herbert@13thfloor.at
Cc: seanlkml@rogers.com, linux-kernel@vger.kernel.org
Subject: Re: .config in bzImage ?
Date: Sat, 2 Aug 2003 21:00:55 +0200 [thread overview]
Message-ID: <20030802210055.556cf98e.diegocg@teleline.es> (raw)
In-Reply-To: <20030802184932.GA12057@www.13thfloor.at>
El Sat, 2 Aug 2003 20:49:32 +0200 Herbert Pötzl <herbert@13thfloor.at> escribió:
> hmm, since ages I use for 2.4.x a small patch, which
> includes the .config in the kernel image (gzipped or
> bzip2ed). this information can be retrieved from the
> procfs by zcat /proc/config.gz or bzcat /proc/config.bz2
> respectively ...
There's something in -ac tree:
x CONFIG_IKCONFIG: x
x x
x This option enables the complete Linux kernel ".config" file x
x contents, information on compiler used to build the kernel, x
x kernel running when this kernel was built and kernel version x
x from Makefile to be saved in kernel. It provides documentation x
x of which kernel options are used in a running kernel or in an x
x on-disk kernel. This information can be extracted from the kernel x
x image file with the script scripts/extract-ikconfig and used as x
x input to rebuild the current kernel or to build another kernel. x
x It can also be extracted from a running kernel by reading x
x /proc/ikconfig/config and /proc/ikconfig/built_with, if enabled. x
x /proc/ikconfig/config will list the configuration that was used x
x to build the kernel and /proc/ikconfig/built_with will list x
x information on the compiler and host machine that was used to x
x build the kernel. x
next prev parent reply other threads:[~2003-08-02 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 18:36 .config in bzImage ? Sean Estabrooks
2003-08-02 18:49 ` Herbert Pötzl
2003-08-02 19:00 ` Diego Calleja García [this message]
2003-08-02 19:29 ` William Lee Irwin III
2003-08-02 20:21 ` Bernd Eckenfels
2003-08-02 20:28 ` William Lee Irwin III
2003-08-05 6:41 ` Denis Vlasenko
2003-08-05 6:45 ` William Lee Irwin III
2003-08-05 11:54 ` Denis Vlasenko
2003-08-05 14:54 ` Jan-Benedict Glaw
2003-08-02 20:52 ` Alan Cox
2003-08-02 21:12 ` Randy.Dunlap
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=20030802210055.556cf98e.diegocg@teleline.es \
--to=diegocg@teleline.es \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=seanlkml@rogers.com \
/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;
as well as URLs for NNTP newsgroup(s).