From: Stuart Longland <stuartl@longlandclan.hopto.org>
To: jeremyjin@nucleus.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to know current Kernel Configuration?
Date: Tue, 16 Sep 2003 17:06:25 +1000 [thread overview]
Message-ID: <3F66B671.1020805@longlandclan.hopto.org> (raw)
In-Reply-To: <0e851eca491344bebdb7b1a70a1bc608.jeremyjin@nucleus.com>
-----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.
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
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.
- --
+-------------------------------------------------------------+
| Stuart Longland stuartl at longlandclan.hopto.org |
| Brisbane Mesh Node: 719 http://stuartl.cjb.net/ |
| I haven't lost my mind - it's backed up on a tape somewhere |
| Griffith Student No: Course: Bachelor/IT (Nathan) |
+-------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/ZrZxIGJk7gLSDPcRAg5/AJ0d9VzrldoRxWbEeaGMW4KIP5dMpgCePHjw
wmkxGNq+SthHSBSeo+XQBKY=
=XfjP
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-09-16 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 5:29 jeremyjin
2003-09-16 7:06 ` Stuart Longland [this message]
2003-09-16 9:48 ` jw schultz
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=3F66B671.1020805@longlandclan.hopto.org \
--to=stuartl@longlandclan.hopto.org \
--cc=jeremyjin@nucleus.com \
--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
all inboxes | Powered by JetHome®