From: Bill Longman <bill.longman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] genkernel without oldconfig
Date: Mon, 16 Aug 2010 08:00:49 -0700 [thread overview]
Message-ID: <4C6952A1.5050903@gmail.com> (raw)
In-Reply-To: <201008152032.31357.ddjones@riddlemaster.org>
On 08/15/2010 05:32 PM, Daniel D Jones wrote:
> On Sunday, August 15, 2010 12:45:06 Marc Joliet wrote:
>> Am Sun, 15 Aug 2010 12:15:57 -0400
>>
>> schrieb Daniel D Jones <ddjones@riddlemaster.org>:
>>> Is there any way to run genkernel without it running the oldconfig
>>> command? I can work around the issue by saving my .config file to a
>>> different name, then using --xconfig and loading the saved file but it
>>> would be nice to just tell it not to alter the existing .config file.
>>> It may be that I'm just missing it but man pages and Google have not
>>> provided a solution.
>>
>> Yes, the configuration file has an appropriate option:
>>
>> # Run 'make oldconfig' before compiling this kernel?
>> OLDCONFIG="no"
>>
>> HTH
>
> It did indeed help. I was looking for a command line argument. Didn't even
> think of the config file. Thank you!
I've never seen this before, either. Thanks for the tip, Marc.
Daniel, how do you use genkernel? I've found that I need to run "make
oldconfig" or, my preference, "make silentoldconfig" by hand before I
ever use genkernel. I copy my old .config to the new kernel directory,
run silentoldconfig, then I run genkernel. Is that the problem you're
facing or do you see changes between invocations of genkernel?
next prev parent reply other threads:[~2010-08-16 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 16:15 [gentoo-user] genkernel without oldconfig Daniel D Jones
2010-08-15 16:45 ` Marc Joliet
2010-08-16 0:32 ` Daniel D Jones
2010-08-16 15:00 ` Bill Longman [this message]
2010-08-16 20:46 ` Marc Joliet
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=4C6952A1.5050903@gmail.com \
--to=bill.longman@gmail.com \
--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