From: "Herbert Pötzl" <herbert@13thfloor.at>
To: Sean Estabrooks <seanlkml@rogers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: .config in bzImage ?
Date: Sat, 2 Aug 2003 20:49:32 +0200 [thread overview]
Message-ID: <20030802184932.GA12057@www.13thfloor.at> (raw)
In-Reply-To: <093901c35924$f3040ed0$7f0a0a0a@lappy7>
On Sat, Aug 02, 2003 at 02:36:12PM -0400, Sean Estabrooks wrote:
> There was some talk of the .config file being included
> within bzImage. Did this ever happen? If so, how
> does one extract the .config from the resulting image?
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 ...
you can get the patch for recent 2.4.x kernels from
my pages http://www.13thfloor.at/VServer/Patches.shtml
(they are 03_kconfig* in the patchsets)
for example for 2.4.22-pre10, this would be ...
http://www.13thfloor.at/VServer/patches-2.4.22-p10c17/03_kconfig-2.4.22-pre3.patch.bz2
HTH,
Herbert
> Cheers,
> Sean
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-08-02 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 18:36 Sean Estabrooks
2003-08-02 18:49 ` Herbert Pötzl [this message]
2003-08-02 19:00 ` Diego Calleja García
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=20030802184932.GA12057@www.13thfloor.at \
--to=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
all inboxes | Powered by JetHome®