From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: How to know current Kernel Configuration?
Date: Tue, 16 Sep 2003 02:48:16 -0700 [thread overview]
Message-ID: <20030916094816.GE30333@pegasys.ws> (raw)
In-Reply-To: <3F66B671.1020805@longlandclan.hopto.org>
On Tue, Sep 16, 2003 at 05:06:25PM +1000, Stuart Longland wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> jeremyjin@nucleus.com wrote:
>
> | And I want to keep most configuration settings because I think these
> settings should be pretty good,
> | how can I know the current configuration of the current kernel? I know
> make has a option "make oldconfig",
> | but seems like it is the old configuration of the last times "make",
> not the one of current running kernel.
>
> Ahh, it's using the default configuration from the linux source, I'm not
> sure where it's stored, somewhere in arch/i386... as far as I know.
The 2.4 default config is in arch/$ARCH/defconfig
> However, Red Hat stores their version of the .config file in /boot as
> config-`uname -r`. So copy this to your kernel source directory as
> .config, then try make oldconfig, etc...
>
> A quick way of doing this... (assuming you are in the kernel source
> directory)
>
> # cp /boot/config-`uname -r` .config
That gets really messy or unreliable fast if you have more
than one kernel. And if you build your own you better have
more than one.
>
> Then run...
>
> # make oldconfig
> # make xconfig, menuconfig or config - optional
> # make dep bzImage modules modules_install - usual build procedure.
>
> | Is there any command to list all current running linux kernel
> configuration which is used to compile that version?
> Not in 2.4.x as far as I know, but there is a virtual file in /proc
> (/proc/ikconfig or something like that I think) that does this.
it is CONFIG_PROC_CONFIG
menuconfig: filesystems->/proc/config.gz
right below /proc filesystem support.
Came in really handy for me when i recently applied SuSE's
kernel update rpm and it overwrote the kernel tree including
.config. Fortunately i had turned it on in an earlier
build. If it wasn't enabled it won't do you any good.
Although understating the size a bit (mine are 4K-6KB) the
help text is to the point:
The cost is around 1K-4K of running memory. Only say
no if you really can't spare this. You can sneeze
and lose more on memory than this.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
prev parent reply other threads:[~2003-09-16 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 5:29 How to know current Kernel Configuration? jeremyjin
2003-09-16 7:06 ` Stuart Longland
2003-09-16 9:48 ` jw schultz [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=20030916094816.GE30333@pegasys.ws \
--to=jw@pegasys.ws \
--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