Hello,
I think I've found a clue about this bug :
the man page of kernel-img.conf says :

do_symlinks

By default, the kernel image post installation script shall create or
update the /vmlinuz and /vmlinuz.old symbolic links. This is true if
a /vmlinuz link already exists, however, in absence of /vmlinuz, the
script looks to see if this configuration file exists. If it does
not, the configuration script asks the user whether to create the
symbolic link, and stashes the answer in a newly created
/etc/kernel-img.conf. If the configuration file already exists, and
if this option is set to No, no symbolic link is ever created. This
for people who have other means of booting their machines, and do not
like the symbolic links cluttering up their / directory. Defaults to
Yes.


So I tried to delete /vmlinuz and /initrd then I ran dpkg-reconfigure
linux-image-2.6.22-3-686

I got :

inding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.22-6.lenny1 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.22-6.lenny1 was configured last, according to dpkg)


So it seems that even with do_symlinks=yes in /etc/kernel-img.conf the
installation script doesn't check the existence of symlinks in / and
doesn't create them if they don't exist. In this case the system won't
be able to boot anymore






--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org