Argh. I see the new version is present, but it didn't reboot as it should have. I hate it when the kernel file isn't changed from the old uname. I have a new boot file /boot/vmlinuz-4.9.0-8-amd64 and I'm running an older kernel Linux falcon 4.9.0-8-amd64 Only the date on the file in /boot and uptime tells me I'm not running that new kernel.
Mystery as to why it has not auto-scheduled a reboot. On Wed, Oct 3, 2018 at 10:58 AM francis picabia <fpica...@gmail.com> wrote: > > When I do apt-get update && apt-get upgrade to get > the new kernel which is part of DSA-4308-1 (released Oct 1), > I get nothing available. > > I have in sources.list: > > deb http://mirror.csclub.uwaterloo.ca/debian/ stretch main contrib > non-free > deb-src http://mirror.csclub.uwaterloo.ca/debian/ stretch main contrib > non-free > > deb http://security.debian.org/debian-security stretch/updates main > contrib non-free > deb-src http://security.debian.org/debian-security stretch/updates main > contrib non-free > > I've tried apt-get clean and even apt-get dist-upgrade > Nothing makes any difference and no packages are reporting held back. > > System has been running fine for several months. Another system with the > same > sources.list was recently rebooted with the updated kernel. Both are on > unattended upgrades, so I was surprised the one system isn't getting the > update. > > I can install new packages fine. > > Are there steps I can use to debug this issue or force it to really see > what is available? > > mtr shows I can get to the host alias security.debian.org > > >
