From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo-sources menuconfig feature/weirdness
Date: Fri, 24 Feb 2012 23:02:38 +0000 [thread overview]
Message-ID: <20120224230238.03192b47@digimed.co.uk> (raw)
In-Reply-To: <20120224221124.GB27406@badass.gateway.2wire.net>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On Fri, 24 Feb 2012 14:11:24 -0800, ny6p01@gmail.com wrote:
> Or just import .config into the 'New' directory, and run plain ol' make
> menuconfig. Menuconfig will import what it can from the old config. From
> what I've read of the docs, make oldconfig is the dangerous part that
> should be avoided between substantial kernel updates.
make oldconfig is not the risk, importing the old config is. oldconfig
tries to convert the old config to suit the new kernel, with a success
rate probably in excess of 99%, despite what has been written about it.
Using the old .config without make oldconfig is a good way of getting
the worst of both worlds.
--
Neil Bothwick
Windows Error #56: Operator fell asleep while waiting.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-24 23:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 8:10 [gentoo-user] gentoo-sources menuconfig feature/weirdness Coert Waagmeester
2012-02-23 8:25 ` Mick
2012-02-23 8:51 ` Coert Waagmeester
2012-02-23 9:17 ` Neil Bothwick
2012-02-23 10:48 ` Coert Waagmeester
2012-02-23 11:08 ` Alan McKinnon
2012-02-23 11:16 ` [gentoo-user] SOLVED " Coert Waagmeester
2012-02-23 11:25 ` Alan McKinnon
2012-02-23 12:24 ` J. Roeleveld
2012-02-23 14:04 ` Mark Knecht
2012-02-24 22:11 ` [gentoo-user] " ny6p01
2012-02-24 23:02 ` Neil Bothwick [this message]
2012-02-24 23:44 ` David W Noon
2012-02-24 23:49 ` Dale
2012-02-25 1:52 ` ny6p01
2012-02-25 2:10 ` Dale
2012-02-25 2:50 ` Pandu Poluan
2012-02-25 11:38 ` Dale
2012-02-24 22:08 ` ny6p01
2012-02-23 9:25 ` William Kenworthy
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=20120224230238.03192b47@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