"Close enough." Anyway, to my way of thinking the answer is
definitely "yes." You always want to be absolutely certain that every part of the kernel which could possibly be affected by your change, however slight, is always incorporated in every scrap of binary code whether in the resident kernel or in any module. It only takes
one screw-up to hose your system badly.
The procedure I always use, quite religiously, is as follows:
- Make a dated backup copy (not hidden) of the .config hidden file, in some far-away directory (mine's under /root/kernel_configs, a directory name of my own choosing). Write-protect this copy so that it will never be overwritten (by you).
- Temporarily rename .config to some other name.
- make distclean
- Rename the file back.
- The usual make .. make install sequence.
- LQQK in the target locations to make sure that the kernel image is new, and that all of the modules are new. (Do not assume... actually look.)
Even though the kernel is an extremely
important program, it's actually not a
big program, nor does it take an extraordinary amount of time to compile.
