>>> I tried closely comparing the current working kernel with newly built >>> one. I mean side by side with `make menuconfig' running in both sources. >>> I cannot tell what it is I'm overlooking. >> >> Please do not do this. Instead emerge kccmp to compare kernel >> configurations! It is much easier...trust me, I tried brute-force as >> well! > > Thanks for the tip... that tool does look useful. At least for > kernel comparison I think it might beat the poop out of the ediff mode > in emacs. Although the emacs tools are better in general. > > I managed to get the kernel figured out... (with plenty of help here) > but I think I'll tinker with kccmp, see how it works, and be ready for > next time.
It's really easy. You just run it with two configuration files as inputs, and it gives a nice X display with different settings, and then settings that are only in one config or the other (resulting from different kernel versions or sub-config options). > Answering a dozen or so questions on the cmdline beats the poop out of > flopping around in menuconfig, or even worse, 2 instances of > menuconfig. > > What is really maddening is that I once knew how to do the stuff with > .config and `make oldconfig'. Here lately I seem to forget things I > once knew if I don't use the knowledge for a mnth or two. > I always do it from the command line with a web-browser searching http://cateee.net/ for any config I don't know what it is. ~daid
