There doesn't seem to be a switch to prevent killing a manually created menu.lst

[Robert Millan]

On Mon, May 21, 2007 at 09:22:31AM +0200, Matthias Schniedermeyer wrote:
> Hi
> 
> 
> I use SID and in the last update the package "memtest86+" was updated.
> As part of its postinst it called "update-grub" which in turn totally fucked up my manually crafted configuration.
> 
> So to prevent such accidents in the future i "dpkg-divert"ed the update-grub-script out of the way and replaced it with "/bin/true", as there doesn't seam to exist a other (obvious and/or elegant)
> method to make update-grub a no-op.
> 
> IMO a /etc/default/grub to make update-grub a no-op is missing.

Did you really mean menu.lst (grub legacy), or grub.cfg (grub2)?  The matter
of your concern is addressed quite differently in each of these.

-- 
Robert Millan

My spam trap is honeypot at aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.