Re: kernel-package and moving the old vmlinuz
On Fri, Jan 04, 2002 at 06:48:36PM +0200, Shaul Karl wrote:
| kernel-package is not behaving the way I expected it with regard to
| moving the old vmlinuz to vmlinuz.old.
| Can you help identifying what am I doing wrong?
|
| The point is that I had
| /vmlinuz -> /boot/vmlinuz-2.2.20 and
| /vmlinuz.old -> /boot/vmlinuz-2.2.19pre17,
| where the 2.2.20 was installed from kernel-image-2.2.20_custom.1.0_i386.
| deb.
| Next I installed kernel-image-2.2.20_custom.2.0_i386.deb and got both
| vmlinuz and vmlinuz.old pointing to /boot/vmlinuz-2.2.20.
Of course. It renamed 'vmlinuz' (which points to
/boot/vmlinuz-2.2.20) to 'vmlinuz.old. Then it created 'vmlinuz' to
point to the new image (/boot/vmlinuz-2.2.20).
| Why then I got both vmlinuz and vmlinuz.old pointing to the same kernel
| image?
The problem is that you created two packages both containing
/boot/vmlinuz-2.2.20 but not conflicting with each other. This is
bad! To correct it, use the following make-kpkg command. It includes
the version both as part of the kernel image's filename and also as
the Version: of the package.
fakeroot make-kpkg clean && fakeroot make-kpkg --config=xconfig --append-to-version=-custom.1 --revision=custom.1 kernel_image kernel_doc kernel_headers
The key is to use both --append-to-version (for the filename) and
--revision (for the package version).
-D
--
A)bort, R)etry, D)o it right this time
Reply to: