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