From: Albert Hopkins <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] make oldconfig necessary?
Date: Mon, 01 Aug 2011 07:52:32 -0400 [thread overview]
Message-ID: <1312199552.27562.5.camel@localhost.localdomain> (raw)
In-Reply-To: <55C88D75-B848-4C80-801B-9D52A5844886@uberpenguin.net>
On Sunday, July 31 at 21:23 (-0500), Jeremy McSpadden said:
> Better to run make oldconfig. It merges the changes.
>
> --
> Jeremy McSpadden
> deface@uberpenguin.net
>
>
>
>
> On Jul 31, 2011, at 9:06 PM, Pandu Poluan 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`?
> >
Agreed, although it should be possible to go straight to menuconfig,
what I think that does is basically says 'n' to all the changes, and you
never get to see what you said no to. (Unless you have a *very* good
memory and peruse though everything in menuconfig (but that isn't
entirely correct either since some menu options will not be visible
since you implicitly said not to them).
Usually, I just do an oldconfig after a kernel upgrade. If I also need
to explicitly enable/disable something, then i do an oldconfig followed
by a menuconfig.
next prev parent reply other threads:[~2011-08-01 11:53 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 [this message]
2011-08-01 2:44 ` Mark Knecht
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=1312199552.27562.5.camel@localhost.localdomain \
--to=marduk@letterboxes.org \
--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