For the most part, make-kpkg is "A Good Thing". I have a question on how it
would handle remaking the same kernel version with a new .conf entry that would
break the old kernel running the new modules.
User has 2.0.29 and recompiles for multiprocessor support. Makes a new kernel
package with make-kpkg, and installs it with dpkg. The installation moves the
old kernel out of the way, installs the new one, installs the new modules and
User boots the new kernel and realizes they made a major goof. It does not
boot. They try to boot the old kernel and the modules no longer work. Same
kernel version but the modules are incompatable.
I have not done this but I am woring with SEUL and it is a scenario that has
come up. Does make-kpkg flag the modules in some way and put them in a
different location if it detects that the new modules are incompatable with the
old ones ... does it even look, is this an area that we can help?
If NT is the answer, you didn't understand the question. (NOTE: Stolen sig)
Debian/GNU Linux ... the maintainable operating system.