From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with "make oldconfig" 2.6.30-8 ==> 2.6.31
Date: Wed, 10 Mar 2010 14:35:23 +0000 [thread overview]
Message-ID: <20100310143523.2e53b74b@digimed.co.uk> (raw)
In-Reply-To: <4B97AC47.5030806@libertytrek.org>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
On Wed, 10 Mar 2010 09:27:19 -0500, Tanstaafl wrote:
> > I see what you mean about the guide and consider it wrong, especially
> > for an advanced section. You are more likely to run into problems
> > when not reusing your old config that when using make oldconfig.
>
> But... my understanding is that, by copying your old .config to the new
> kernel dir before running make menuconfig, you *are* reusing your old
> config... I sure hope I'm not reading *that* wrong. ;)
No you're not. But it is far easier to miss important changes without
oldconfig to point them out to you by shoving them in your face.
>
> > Even the comment about context isn't really true, as oldconfig shows
> > some context and the same help that menuconfig does.
>
> Ok... well, this is how I've always done it, and I'm comfortable with
> it, so don't see a reason to change.
Each to their own.
> Maybe I'll try running make oldconfig one day just to see how it
> differs...
It's not black magic, it just shows you any new options that are not
present in your config, offers you choices along with a default and a
chance to read the help text for that option. If you're feeling paranoid,
diff the config it generates with the one you started with.
--
Neil Bothwick
BING But It's Not Google
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-10 14:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 1:36 [gentoo-user] Problem with "make oldconfig" 2.6.30-8 ==> 2.6.31 Walter Dnes
2010-03-10 9:02 ` Kaddeh
2010-03-10 13:22 ` Tanstaafl
2010-03-10 13:38 ` Dale
2010-03-10 13:46 ` Tanstaafl
2010-03-10 14:07 ` Alan McKinnon
2010-03-10 14:19 ` Tanstaafl
2010-03-11 10:16 ` Alan McKinnon
2010-03-10 13:47 ` Neil Bothwick
2010-03-10 13:56 ` Tanstaafl
2010-03-10 14:09 ` Neil Bothwick
2010-03-10 14:27 ` Tanstaafl
2010-03-10 14:35 ` Neil Bothwick [this message]
2010-03-10 15:46 ` Tanstaafl
2010-03-10 15:53 ` Paul Hartman
2010-03-10 14:09 ` Mick
2010-03-10 14:37 ` Neil Bothwick
2010-03-10 14:03 ` Alan McKinnon
2010-03-10 13:55 ` Mick
2010-03-11 13:03 ` Walter Dnes
2010-03-11 13:20 ` Neil Bothwick
2010-03-11 13:23 ` Jonathan
2010-03-11 23:38 ` [gentoo-user] Re: [solved] " Walter Dnes
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=20100310143523.2e53b74b@digimed.co.uk \
--to=neil@digimed.co.uk \
--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