From: Erik Mouw <erik@harddisk-recovery.com>
To: george young <gry@ll.mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/config.z disappeared in 2.4.24
Date: Mon, 2 Feb 2004 17:57:21 +0100 [thread overview]
Message-ID: <20040202165721.GE1078@bitwizard.nl> (raw)
In-Reply-To: <20040202115224.64063795.gry@ll.mit.edu>
On Mon, Feb 02, 2004 at 11:52:24AM -0500, george young wrote:
> [SuSE x86 linux 8.2, 2.4.24 kernel building]
[...]
> The /proc/config.z file seems to have disappeared! Is there some
> config parameter that enables this? Or has it gone away between 2.4.20
> and 2.4.24?
It didn't disappear, it has never been there. Both RedHat and SuSE have
a patch that include the kernel .config in the image itself, but that
feature is not in the official 2.4 kernel (it is however in 2.6).
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
prev parent reply other threads:[~2004-02-02 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 16:52 /proc/config.z disappeared in 2.4.24 george young
2004-02-02 16:57 ` Erik Mouw [this message]
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=20040202165721.GE1078@bitwizard.nl \
--to=erik@harddisk-recovery.com \
--cc=gry@ll.mit.edu \
--cc=linux-kernel@vger.kernel.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