From: Dale <dalek1967@bellsouth.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] make oldconfig
Date: Tue, 05 Aug 2008 14:23:06 -0500 [thread overview]
Message-ID: <4898A89A.9050903@bellsouth.net> (raw)
In-Reply-To: <6142e6140808050439q715ac701u9941cae2bf717bb5@mail.gmail.com>
Daniel Pielmeier wrote:
> 2008/8/4, James <wireless@tampabay.rr.com>:
>
>> Hello,
>>
>> It seems like I remember that 'make oldconfig' is not
>> needed any more, to pass the current (booted) kernel
>> option to the .config for building a new kernel.
>>
>> Of is 'make oldconfig' still a good idea?
>>
>>
>> James
>>
>
> At least in the kernel Makefile there is no hint about /proc/config.gz
> which contains the running kernel configuration, so I think make
> oldconfig or your favourite kernel configuration tool is still needed.
> If there is no .config or .config.old it will load a default
> configuration which is probably not what you want.
>
>
>
Having a config in /proc is a option in the kernel. You just have to
turn it on. It is under the General setup as "Enable access to .config
through /proc/config.gz". I have mine here:
root@smoker / # ls -al /proc/config*
-r--r--r-- 1 root root 10060 2008-08-05 14:19 /proc/config.gz
root@smoker / #
It can prove helpful at times.
Dale
:-) :-)
next prev parent reply other threads:[~2008-08-05 19:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 21:04 [gentoo-user] make oldconfig James
2008-08-04 17:11 ` Eric Martin
2008-08-04 22:52 ` [gentoo-user] " Nikos Chantziaras
2008-08-05 11:15 ` Eric Martin
2008-08-05 11:39 ` [gentoo-user] " Daniel Pielmeier
2008-08-05 19:23 ` Dale [this message]
2008-08-05 15:48 ` Eric Martin
2008-08-05 20:54 ` Dale
2008-08-06 1:58 ` [gentoo-user] " James
2008-08-06 2:34 ` M. Sitorus
2008-08-06 2:38 ` Dale
2008-08-06 7:08 ` Daniel Pielmeier
2008-08-09 20:35 ` james
2008-08-09 21:50 ` »Q«
2008-08-06 9:28 ` Thanasis
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=4898A89A.9050903@bellsouth.net \
--to=dalek1967@bellsouth.net \
--cc=gentoo-user@lists.gentoo.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