From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] make oldconfig necessary?
Date: Sun, 31 Jul 2011 19:44:59 -0700 [thread overview]
Message-ID: <CAK2H+ecWdU4Nq_9UgxQqAOh7SmxCbJJHui_17cFLWQYHvdSzvA@mail.gmail.com> (raw)
In-Reply-To: <CAA2qdGWo4XET9Ahu9zmR6Zj-4O51fy9pAHTSf+a-D=Km5hD0sQ@mail.gmail.com>
On Sun, Jul 31, 2011 at 7:06 PM, Pandu Poluan <pandu@poluan.info> wrote:
> 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`?
>
> Rgds,
It is not necessary but you'll be starting from scratch. Linux often
suggests that's the best thing to do but I've done make oldconfig for
12 years now and never had a problem that I could trace back to using
it. It certainly saves time.
I also ALWAYS run make menuconfig following make oldconfig mainly so I
can exit from menuconfig and get messages (if any) about config
problems.
Hope this helps,
Mark
next prev parent reply other threads:[~2011-08-01 2:46 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 [this message]
2011-08-01 4:16 ` Bill Longman
2011-08-01 11:56 ` David W Noon
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=CAK2H+ecWdU4Nq_9UgxQqAOh7SmxCbJJHui_17cFLWQYHvdSzvA@mail.gmail.com \
--to=markknecht@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