Guido,
Bug number 505609 has been closed by the kernel team. However, the kernel
team is only going to fix the problem for Lenny. To fix the problem in
Squeeze and later releases will require that a hook script of some kind
be added to the lilo package. The problem is that lilo didn't get run
during the kernel upgrade, as it should have been, due to changes in the
kernel maintainer scripts which, for Squeeze and later releases, the
kernel team regards as a feature and not a bug. Their position is that
lilo needs to provide a hook script to make sure lilo gets run during a
kernel upgrade. This bug report will remain open until a lilo package
with a suitable hook script gets uploaded. In the mean time, here's one
way to work around it. (Do this as root.)
(1) Make sure that large-memory is specified in /etc/lilo.conf.
(2) Create a file called /usr/sbin/lilo-update. It should look like this:
#!/bin/sh
# This file is referenced by /etc/kernel-img.conf.
lilo -v >&2
(3) Mark the file executable, like this:
chmod +x /usr/sbin/lilo-update
(4) Edit the file /etc/kernel-img.conf. Make sure that
do_bootloader = yes
is specified in this file (for the sake of "update-initramfs -u"),
then add
postinst_hook = lilo-update
postrm_hook = lilo-update
This will cause lilo to get run when a stock kernel image is installed
or upgraded.
If you are going to use a custom kernel, such as one created
by make-kpkg or "make deb-pkg", then this is not adequate. I recommend
that you read my unofficial kernel building web page,
http://www.wowway.com/~zlinuxman/Kernel.htm, for more complete information
on how to make sure that lilo gets run (as well as other necessary stuff)
when using a custom kernel.
If you have any further questions about this lilo problem, please post
to this bug log (585856).
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
