Re: execution of update-grub in chroots might fail

[Michael Prokop]

* Felix Zielcke <address@hidden> wrote:
> Am Montag, den 14.12.2009, 11:56 +0000 schrieb Colin Watson:
>> On Sun, Dec 13, 2009 at 11:08:04PM +0100, Michael Prokop wrote:
>> > For example postinst of memtest86+ uses:

>> >   if [ "$1" = "configure" ] && [ -x "`which update-grub2 >> 2>/dev/null`" 
>> > ] ; then
>> >       update-grub2
>> >   fi

>> > which is the recommended and suggested way to install grub menu entries.

>> Recommended where? (This implies the existence of documentation on the
>> subject, which I wasn't aware of ...)

> I wonder too why he wrote that. When I talked with him on IRC yesterday,
> I mainly said that using `update-grub || true' would be wrong. And
> neither me nor Robert (at leat until I was on IRC which was though later
> then he wrote this mail) not at all anything that says there's a written
> policy for interacting with GRUB things or even that the above thing is
> the recommended and suggested way.

Sorry, my fault for not being specific enough. I just meant
update-grub itself, nothing else. I was refering to:

18:10:29< nyu> mika: it's intentional. it means add-on packages are free to run 
update-grub to plug their stuff in

>> The simplest fix is to add '&& [ -e /boot/grub/grub.cfg ]' to the
>> test in memtest86+; that is, if the configuration file hasn't
>> been generated already, it shouldn't be updated. (This check is
>> in the memtest86+ postinst in Ubuntu.) This accounts for the
>> OpenVZ problem as well as for other reasons why GRUB might not
>> actually be being used as a boot loader.

Is the memtest86+ maintainer of Debian aware of this (at least
temporary but working) solution or should I ping him?

regards,
-mika-