That is what I thought Wackojacko has the answer in this thread it is
because
of having the vmlinuz and vmlinuz.old symbolic links in /boot it adds
these
as well. I removed them and updated grub manually I did not get the
duplicates put the links back updated grub and there were the duplicates
again. Which sucks because without the links it does not list my newest
kernel in the grub splash screen first so I would have to select it
manually
instead of getting to boot into it without an action on my part.
Stephen
Hi,
that's what I have in my /boot
-rw-r--r-- 1 root root 70797 2007-03-26 18:32 config-2.6.18-4-k7
drwxr-xr-x 2 root root 4096 2007-05-14 09:47 grub
-rw-r--r-- 1 root root 4403522 2006-12-15 10:45 initrd.img-2.6.17-ra2.bak
-rw-r--r-- 1 root root 5025328 2007-05-11 14:24 initrd.img-2.6.18-4-k7
-rw-r--r-- 1 root root 722453 2007-03-27 00:45 System.map-2.6.18-4-k7
-rw-r--r-- 1 root root 1268398 2007-03-27 00:45 vmlinuz-2.6.18-4-k7
as you can see there are no symlinks.
I have removed any other kernel but the recent one in lenny and still
update-grub adds recovery mode duplicates at evry run.
The strange thing I see in that initrd.img-2.6.17-ra2.bak file whose origin
is obscure to me, even if 'ra' is the suffix I use in --revision option when
using make-kpkg.
I have no other custom kernels installed, so I assume it is safe to remove
initrd.img-2.6.17-ra2.bak and send other feedbaks.
regards
raffaele
