also sprach dann frazier <dannf@debian.org> [2009.08.06.2150 +0200]:
> Yeah, rebooting is certainly a good sysadmin practice, esp after a
> significant upgrade, but I just can't think of many packages that
> need to request a reboot from the admin during install/upgrade.
Every. single. one. ;)
> > > I do like the idea of a cronjob that checks periodically to see if
> > > the kernel-that-would-be-booted-next is the same kernel that is
> > > currently booted. It would be able to detect a mismatch introduced
> > > outside of a dpkg operation - for example, if the the user
> > > reconfigures which installed kernel is the default.
> >
> > This is a twist on my proposal. All I wanted is a tool that knocks
> > me over the head like "hey, you installed a new 2.6.30 last week and
> > were to tired or unable to drive to the colo centre, or you were too
> > much of a chicken to do a remote reboot. But you still have to do
> > it. And till then, I'll mail you every day!"
>
> It is a twist (well, an extension), but one I suspect users to
> want. If you are running a 2.6.30 and install an updated 2.6.26 (or
> vice-versa), do you want to be nagged everyday until you reboot? It
> would be preferable to only nag if the default-kernel was updated
> (either by installing 2.6.31 or an updated 2.6.30).
"For the running kernel version (2.6.30 is 2.6.30, so 2.6.30-1-amd64
== 2.6.30-2-amd for this purpose), check if there is an image
package installed that is strictly larger in version than what's
currently running according to /proc/version."
--
.''`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
"... and so he killed Miguel in a rit of fealous jage."
-- inspector clouseau
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)