Re: 2.6.16-1 ==> 2.6.16-2
On Sun, 26 Mar 2006 22:14:44 +0200
Florian Kulzer <florian@molphys.leidenuniv.nl> wrote:
> David Baron wrote:
> > Untarred the -2 onto the linux-source-2.6.16 directory already populated by
> > -1. The make-dpkg showed no compilations per se other than the first few
> > script checks. It then pronounced the image ready, did LDs on the modules
> > (All of them?? Maybe not).
> >
> > Change logs did not state what was changed. Should there have been new
> > compiles or must the thing be "cleaned" each time to update a few pieces or
> > modules?
>
I usually do make and then make-kpkg. I'm not sure as to the current state of
make-kpkg, it used to work using it directly and then it stopped (ignored
changes to the source tree and just repackaged the already compiled code
again). I don't know where it stands now.
Another possibility BTW is that the code that changed is not part of what you
are using in the kernel, or part of the packaging code (pre/post install
scripts). You'll need to diff to clean trees to find out exactly what changed.
> I think make-kpkg will not compile the new sources if it still finds the
> old compiled binaries; it cannot tell in which cases the source has
> changed. "make-kpkg clean" will cause a fresh start, but then everything
> will be recompiled. I think that what you did resulted in the old
> binaries being assembled into a new kernel image.
>
> I am not sure if it is advisable to recompile only some of the modules.
> (Such a thing could probably be achieved by diff-ing the new and old
> source tree and deleting all the binaries for which the source files
> have changed.)
>
> The first thing to look at is
> /usr/share/doc/linux-source-2.6.16/changelog.Debian.gz
> to decide if you need to recompile at all. If you are on i386 then the
> upgrade from 2.6.16-1 will only bring you an updated uploader list,
> which has no influence on the performance of the kernel.
>
> The recommended procedure is to always use the "clean" target before you
> compile a newer version. You can use "nice make-kpkg ..." when you build
> the kernel image, then you can continue to work normally with your
> computer while the new kernel is compiled.
>
> Regards,
> Florian
>
>
Reply to: