Ron Hale-Evans wrote:
Whenever I compile a new kernel, I give it a new version number with
--revision, thus:

  # make-kpkg --revision custom.2.3 kernel_image

...yet the version number of the resulting .deb package stays the same as
the first time I compiled that kernel version's source. In this example, it
would stay at custom.2.0, which was my first kernel 2.2.9 build.

Surely this isn't the right (documented) behavior? The man pages for
make-kpkg aren't much help.

Many thanks to Brad for help with kernel compilation and my ne.o module
problem. It worked fine.

Ron
--
Ron Hale-Evans: [EMAIL PROTECTED] & http://www.apocalypse.org/~rwhe/
     Center for Ludic Synergy & "Kennexions" Glass Bead Game
  & Hexagram-8 I Ching Mailing List & State-Specific Sciences List &
                        Positive Revolution FAQ

--
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

If you use make-kpkg clean then make-kpkg --revision you will not have that problem

The docs under /usr/lib/kernel-package were very helpful when I started out useing the kernel packager
 

-- 
Philip S. Hempel  mailto:[EMAIL PROTECTED]
Linux HardCore http://www.linuxhardcore.com
 


Reply via email to