On Sunday, July 31 at 21:23 (-0500), Jeremy McSpadden said:
> Better to run make oldconfig. It merges the changes. > > -- > Jeremy McSpadden > def...@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.
