Neil Bothwick wrote: > On Fri, 24 Feb 2012 14:11:24 -0800, ny6...@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. > >
Of all the upgrades I have done, I have only had make oldconfig fail once. When I posted here, I think it was Alan that said it was a major change in the kernel menu that messed it up. That was a few years ago. 99% is likely about right. One failure so far and waiting on the next major change in the menu for failure #2. Now watch it fail the very next time I use it. O_o Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
