The following packages have been kept back

[Hal Burgiss]

On Wed, Apr 22, 2009 at 4:06 PM, Brian McKee <brian.mckee at gmail.com> wrote:
> On Wed, Apr 22, 2009 at 3:44 PM, Hal Burgiss <hal at burgiss.net> wrote:

> You did a safe-upgrade rather than a dist-upgrade right?

I did not do the upgrade, so I can't say. I would have guessed
dist-upgrade though.

> You have to specifically allow kernel upgrades - just do the dist-upgrade.
>
> If access to the box is difficult/expensive and/or you are paranoid
> about it, then install that kernel manually without setting it as the
> default in grub.  Then add a cron entry telling the box to reboot in
> say 15 minutes.  Then reboot, telling grub to use the newly installed
> kernel.  If it comes back up fine, cancel the cron job and set the new
> kernel as default.  If it doesn't come back, hopefully it made it up
> enough that cron will reboot it for you to the known working kernel in
> 15 minutes.  If you've got remote KVM of course then you don't need
> this at all.

The system is not terribly far away, so I can get to it. The upgrade
keeps all the old kernels, right?

Thanks Brian.

-- 
Hal