On Sat, 2006-10-21 at 00:07 +0000, Matt Zimmerman wrote:
> Ben, please arrange for future kernels to drop a file or such so that we
> can test its timestamp against the uptime of the system to determine
> whether the kernel has been upgraded since the last reboot (and refuse
> to hibernate in this case).
I thought we had setup the /proc/version_signature file for this very
reason?
Also, it's very easy to test for /var/run/reboot-required, which shows
that some update of the system is requiring a reboot. The largest user
of this file is the kernel. I would be willing to bet that other users
would also be grounds for not hibernating.
So if the hibernation scripts test for /var/run/reboot-required, they
could use this as a means for deciding not to hibernate.
On Sat, 2006-10-21 at 00:07 +0000, Matt Zimmerman wrote:
> Ben, please arrange for future kernels to drop a file or such so that we
> can test its timestamp against the uptime of the system to determine
> whether the kernel has been upgraded since the last reboot (and refuse
> to hibernate in this case).
I thought we had setup the /proc/version_ signature file for this very
reason?
Also, it's very easy to test for /var/run/ reboot- required, which shows
that some update of the system is requiring a reboot. The largest user
of this file is the kernel. I would be willing to bet that other users
would also be grounds for not hibernating.
So if the hibernation scripts test for /var/run/ reboot- required, they
could use this as a means for deciding not to hibernate.