Ben Edwards wrote:
Maybe I am not building the kernel in the most elegent way. I seem to
be using a mixture of EXTRAVERSION and -rev. Not quite sure of the
ramifications of these. Douse the .deb file put stuff into
/lin/modules? What would you recomend to be the best use of
EXTRAVERSION/-re
Ben Edwards wrote:
Colin wrote:
Do a "make-kpkg clean" before changing the revision number should do
the trick.
Ta, that did the trick.
When I dpkg -i the image it complaines that '/lib/modules/2.6.3 (may)
belongs to a old install', I have been moving it to .old but douse this
mean that if I
Colin wrote:
Ben Edwards (lists) wrote:
I use the command
make-kpkg buildpackage -rev Custom.1 kernel_image
to build the kernel, whitch workes fine. However if i use Custom.2 (so
I can keep my old kernel) I get the following:-
blue:/usr/src/linux# make-kpkg buildpackage -rev Custom.2 kernel_im
Ben Edwards (lists) wrote:
I use the command
make-kpkg buildpackage -rev Custom.1 kernel_image
to build the kernel, whitch workes fine. However if i use Custom.2 (so
I can keep my old kernel) I get the following:-
blue:/usr/src/linux# make-kpkg buildpackage -rev Custom.2 kernel_image
I note that
4 matches
Mail list logo
