On Tue, Jun 08, 2010 at 03:48:21PM +0800, Paul Wise wrote: > reassign 584979 update-notifier 0.99.3debian4 > thanks > > On Tue, 2010-06-08 at 09:37 +0200, Josselin Mouette wrote: > > > First this is not update-manager but update-notifier which showed the > > warning. > > My apologies, reassigning. > > > Second, it is obvious that you need to reboot after installing a new > > kernel, regardless of whether or not it overwrote the current modules. > > Our ABI checks are now fine so it’s not expected to crash randomly when > > you upgrade the running kernel in place, but in all cases you need to > > reboot to have the new kernel. > > When I reboot, I'll be rebooting into the same kernel, not the newer > ones from sid/experimental. The latter two are only for testing. So no, > I do not need to reboot. The only case where adding a new kernel would > need a reboot would be where you remove one kernel and install a new one > at the same time. By default you will boot into the newly installed kernel, as long as it's ABI > old ABI. Therefore, you need to reboot in order to take advantage of the new kernel. This message is not a bug, it is a feature.
You can hide all reboot notifications by setting the gconf option
/apps/update-notifier/hide_reboot_notification to true. More is
not possible.
Future versions may be also able to tell you which packages require
a reboot (by reading /var/run/reboot-required.pkgs), for kernel
upgrades the package is always linux-base.
The options for this bug are:
a) close it
b) tag it wontfix
c) you could provide a patch for a gconf option
/apps/update-notifier/hide_reboot_notification_for_packages
which is a list of package names and make update-notifier
only show a reboot notification if /var/run/reboot-required.pkgs
contains one or more packages not in this option.
If prefer (a).
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
pgplqRkrEBzwM.pgp
Description: PGP signature
