Serious problem with kernel update

[Dave Brown]

: There is a VERY SERIOUS problem with kernel updates, which I 
: have brought up in the past and I thought had been fixed!
: 
: NEVER, under ANY circumstances should a lin of a kernel remove 
: the current (or any other) image from the boot directory!!!!!

Personally, I just build my kernels by hand anyway, but I figured
out a way to make sure that "lin linux" doesn't blow away the
previous one: Don't let Lunar know that those files were installed
in the first place.  There doesn't seem to be any concept of
"these files were installed, but don't delete them", so I just had
it install the kernel behind Lunar's back.

Here's my patch:
------------------------------------------------------------------------
diff -r -C 3 kernel/linux/BUILD zlocal/linux-dag/BUILD
*** kernel/linux/BUILD  2003-12-05 14:09:25.000000000 -0800
--- zlocal/linux-dag/BUILD      2004-03-07 11:02:02.000000000 -0800
***************
*** 55,62 ****
    make -j${KMAKES} modules                             &&
    backup_mods_krnl  ${VERSION}-${PVERSION}${EXTENSION} &&
    prepare_install                                      &&
    make  modules_install                                &&
  
!   cp    arch/i386/boot/bzImage   /boot/${VERSION}-${PVERSION}
    
  ) > $C_FIFO 2>&1
--- 55,64 ----
    make -j${KMAKES} modules                             &&
    backup_mods_krnl  ${VERSION}-${PVERSION}${EXTENSION} &&
    prepare_install                                      &&
+   devoke_installwatch                                  &&
    make  modules_install                                &&
  
!   cp    arch/i386/boot/bzImage   /boot/${VERSION}-${PVERSION} &&
!   invoke_installwatch
    
  ) > $C_FIFO 2>&1
------------------------------------------------------------------------

I tried it out on my machine, and it works as desired:
kernel-removal took place upon reinstallation.

--Dave