Bug#481542: grub2: please user triggers

[Joey Hess]

Felix Zielcke wrote:
> >IMHO it's important to consider how triggers would handle a situation
> >such as an apt run that removed the running kernel added a new kernel,
> >and then failed. In this case, the grub trigger might not run, which
> >would leave a menu.lst that contained only a nonexistent kernel.
> 
> Well if removing the current installed kernel suceeded, but installing the new one failed,
> then I think you don't have any kernel at all in /boot

I didn't say that adding the new kernel failed. A later package could
fail.

Or the power could fail before dpkg got around to calling the triggers.

Once apt trigger deferral is implemented, all the triggers will run at
the very end of the apt run, which can be quite a long time after the
kernel packages are removed and installed.

-- 
see shy jo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20080731/9cffa426/attachment.pgp