*- On 13 Sep, John Davis wrote about "make-kpkg doesn't make different kernel
source revs."
> Hello
>
> Why is that when I build a new kernel via make-kpkg, it doesn't make a
> new kernel rev.
>
> Scenario:
> Previously, I built a new kernel using:
> make-kpkg --rev Custom.1.0 kernel_image
> This command built my kernel and put an file in my /usr/src
> directory called. kernel-image-2.0.36_1.00_i386.deb.
>
> Then I built a newer kernel using:
> make-kpkg --rev Custom.2.0 kernel_image
> This command did change the date on the existing kernel package
> but did not call it kernel-image-2.0.36_2.00_i386.deb nor did it
> put the word custom in file name either.
>
> Is this the way this thing is supposed to work?
>
Yes. According to the make-kpkg man page
--revision number
Sets the Debian revision number for the packages
produced to the argument number. This has certain
constraints: It only has an effect during the con
figure phase (in other words, if a file called
stamp-configure exists, this option has no effect
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-- run make-kpkg clean or manually remove
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
stamp-configure for it to have an effect). So, if
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
you re-run make-kpkg with a different revision num
ber, you have to reconfigure the kernel. Secondly,
And according to the /usr/doc/kernel-package/README.gz file the
suggested order is:
1% cd <kernel source tree>
2% make config # or make menuconfig or make xconfig and configure
3% make-kpkg clean
4% fakeroot make-kpkg --revision=custom.1.0 kernel_image
(if running as non-root user)
> Other simple questions:
> 1. When I used to do regular kernel builds, I used to do a
> make dep; make clean; make zImage, make modules; make
> modules_install.
> If I build kernels the debian way (aka make-kpkg), do I still need to
> do this? How about cleaning or rebuilding the dependicy list? ie. do I
> need to a make clean; make dep before I do the make-kpkg?
>
No. It is all taken care of with the above 3 commands.
> 2. Does apt-get dist-upgrade get new kernel patches? Is there a way to
> get new kernel patches?
>
No. You must manually grab and apply them yourself. The
scripts/patch-kernel script in the kernel source is great for that.
--
Brian
---------------------------------------------------------------------
Mechanical Engineering [EMAIL PROTECTED]
Purdue University http://www.ecn.purdue.edu/~servis
---------------------------------------------------------------------
