On Thu, Feb 23, 2012 at 01:08:22PM +0200, Alan McKinnon wrote: > On Thu, 23 Feb 2012 12:48:35 +0200 > Coert Waagmeester <lgro...@waagmeester.co.za> wrote: > > > On 02/23/2012 11:17 AM, Neil Bothwick wrote: > > > On Thu, 23 Feb 2012 10:51:43 +0200, Coert Waagmeester wrote: > > > > > >> The only thing I can currently think of is maybe the kernel config > > >> files in /boot? > > > > > > I'd say it's more likely to be getting it from /proc/config.gz. > > > > > > But why start with a clean config each time? That means you have > > > plenty of opportunities to produce a broken kernel on every update. > > > > > > > > > > Is there a way to import old config files with newer kernel sources? > > I tried it once by simply copying .config into the newer src dir, but > > I read somewhere that there could be incompatibilities. > > > > That is exactly how you do it. Copy a .config over and run make > oldconfig > > Yes, there could be incompatibilities. This might happen once every few > years when you do an upgrade over 10 version numbers. But that can be > fixed. > > Not doing it this way means a very high likelyhood of the machine not > booting with every single upgrade, plus the huge amount of work it > takes to go through everything in menuconfig. > > The choices are simple, > > - low risk of occasional breakage > - high risk of frequent breakage > > > > -- > Alan McKinnnon > alan.mckin...@gmail.com > >
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. Terry
