From: David W Noon <dwnoon@ntlworld.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] make oldconfig necessary?
Date: Mon, 1 Aug 2011 12:56:35 +0100 [thread overview]
Message-ID: <20110801125635.248b249a@memphis.local> (raw)
In-Reply-To: <CAA2qdGWo4XET9Ahu9zmR6Zj-4O51fy9pAHTSf+a-D=Km5hD0sQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 1 Aug 2011 09:06:17 +0700, Pandu Poluan wrote about
"[gentoo-user] make oldconfig necessary?":
>Let's say I have a .config from an older kernel version (for example,
>2.6.38), and now I want to install a newer kernel (let's say, 3.0).
>
>Is it necessary to first do `make oldconfig`, or is it safe to go
>directly to `make menuconfig`?
For some years now, make menuconfig has performed a silent make
oldconfig before it brings up the menu. I stopped using make oldconfig
in about 2007, after I was confident that the change to make menuconfig
was working.
- --
Regards,
Dave [RLU #314465]
======================================================================
dwnoon@ntlworld.com (David W Noon)
======================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iEYEARECAAYFAk42lHgACgkQRQ2Fs59Psv8qGwCeMv0fJ2mF8WcPm620U3m2iM5Y
usYAnR2lUFi2jgBCmLDOIqAEZ22tzM7m
=uV/i
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-08-01 11:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 2:06 [gentoo-user] make oldconfig necessary? Pandu Poluan
2011-08-01 2:23 ` Jeremy McSpadden
2011-08-01 2:42 ` Dale
2011-08-01 11:52 ` Albert Hopkins
2011-08-01 2:44 ` Mark Knecht
2011-08-01 4:16 ` Bill Longman
2011-08-01 11:56 ` David W Noon [this message]
2011-08-01 14:09 ` [gentoo-user] " Grant Edwards
2011-08-01 14:13 ` Michael Mol
2011-08-01 14:39 ` Pandu Poluan
2011-08-01 16:58 ` David W Noon
2011-08-01 21:41 ` Peter Humphrey
2011-08-01 16:00 ` [gentoo-user] " kashani
2011-08-01 20:26 ` Michael Orlitzky
2011-08-01 20:38 ` [gentoo-user] " Grant Edwards
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=20110801125635.248b249a@memphis.local \
--to=dwnoon@ntlworld.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