On Sat, 08 Jan 2000, matt garman wrote: > my /etc/lilo.conf, but /vmlinuz is a symlink into /boot, which hadn't > been updated to point to the new kernel. > > I thought when I built a kernel with make-kpkg and installed the > resulting .deb with dpkg, that either /etc/lilo.conf was updated to see > the new kernel, or the /vmlinuz symlink was updated. Or am I mistaken?
I've noticed the same problem. Looks like a (very recent) bug in kernel-package. Please report it to the bug tracking system. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
