On 11/04/2009 06:16 AM, james wrote: > Graham Murray <graham <at> gmurray.org.uk> writes: > > You have to copy the .config from the running (old) >> kernel to the new kernel directory before running make oldconfig. If you >> start with the default config, then you have to run make menuconfig (or >> config or xconfig) to customise it every time. > > > Hmmmmm, > > > I thought when you install a new kernel, you just change the symbolic link. > > example (old kernel linux-2.6.30-gentoo-r4) > New kernel (linux-2.6.30-gentoo-r5) > > > cd /usr/src > rm linux > ls -sf /usr/src/linux-2.6.30-gentoo-r5 linux > cd linux > make menuconfig
Well, if you really want to use menuconfig first, you need to repeat the entire configuration process from the beginning. Make oldconfig is there exactly so you *don't* need to repeat everything manually. > At this point the new kernel sources (linux-2.6.30-gentoo-r5) > automatically copies over the .config from the version > of the kernel you are actually running... That sentence doesn't make sense. You said the sources automatically copy the .config -- but the sources don't do anything. Only a program could do something automatically, not source code files. It may be that genkernel does something like that, but I've never used it so I don't know. If you are building your kernel manually (as you seem to be doing) then *you* need to copy the .config from the old sources over to your new kernel source directory and *then* do make oldconfig. That's when the magic happens, not before. You'll see lots of interesting stuff if you run 'make help' in the kernel source directory.
