update-grub is run because you asked for it. Please look in
/etc/kernel-img.conf, you'll probably find:
Which I have never changed or even opened.
And this has happened on 2, yes 2 different systems.
So if this is not aptitude, there is still an issue that using aptitude
for a standard upgrade overwrites an important configuration file.
The same would have happened by using apt-get
Now *if* I had made the changes, yes, the I should know the impact of
what I did, but since this is a default setup, somewhere, the end
effect is that using aptitude on Stable, which should be safe, can
quickly render a system unbootable.
I suggest you also read the comments in /boot/grub/menu.lst. They
explain very well that some sections of the file are likely to be
overwritten when the file is regenerated by update-grub.
I guess that the update you made installed a new kernel image...which
trigger an update of the grub menu file when the postinst script of
the kernel image package is run.
The postinst_hook may be set, but *I* never set it and on the effect
systems, I have never done a thing with the kernel or changed any
kernel settings.
Then something else changed it...but I have no idea what did so. The
file does not belong to any package.
Certainly the bug is not, definitely not, an aptitude bug. You can't
blame aptitude for every problem happening with packages it installs.
mean where should I file the issue that during aptitude upgrade
update-grub is run as a default behavior? This is not documented or
To a -user list, to the kernel development list...whatever.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
