From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: William Lee Irwin III <wli@holomorphy.com>,
Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: .config in bzImage ?
Date: Tue, 5 Aug 2003 09:41:35 +0300 [thread overview]
Message-ID: <200308050632.h756W5j17568@Port.imtp.ilyichevsk.odessa.ua> (raw)
In-Reply-To: <20030802202803.GD32488@holomorphy.com>
On 2 August 2003 23:28, William Lee Irwin III wrote:
> In article <20030802192957.GC32488@holomorphy.com> you wrote:
> >> IIRC this hit current 2.6 bk recently, which probably helps _someone_
> >> with administration (and may very well save me some reboots to get into
> >> kernels with known .configs).
>
> On Sat, Aug 02, 2003 at 10:21:31PM +0200, Bernd Eckenfels wrote:
> > Of course you can simply place the .config along the kernel and the
> > System.map in /boot, too.
>
> Which requires having some way to associate the running kernel to those
> files.
bash-2.03# ls -l /boot
drwxr-xr-x 2 root root 1024 Jan 28 2003 2.4.20
drwxr-xr-x 2 root root 1024 Nov 2 2002 2.4.20-pre11csum_t
drwxr-xr-x 2 root root 1024 Oct 30 2002 2.4.20-pre11csumtest
drwxr-xr-x 2 root root 1024 Jul 17 08:10 2.4.21
drwxr-xr-x 2 root root 1024 Jul 17 15:15 2.4.21-ep
--
vda
next prev parent reply other threads:[~2003-08-05 6:42 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
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 [this message]
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=200308050632.h756W5j17568@Port.imtp.ilyichevsk.odessa.ua \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=ecki@calista.eckenfels.6bone.ka-ip.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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).