Re: Why doesn't new linux kernel appear from security two days after release?
On Wed, Oct 03, 2018 at 11:16:36AM -0300, francis picabia wrote:
> I hate it when the kernel file isn't changed from the old uname.
Keeping the same ABI is *helpful*, because people don't have to rebuild
their third-party (dkms) modules. Bumping the ABI for security updates
is awful, and I'm glad Ben Hutchings has been going out of his way to
avoid that (based on the changelogs).
> 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.
The information you seek is in "uname -a" output, or "uname -v" if you
want to isolate it a bit more.
wooledg:~$ uname -v
#1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21)
root@img3:~# uname -v
#1 SMP Debian 4.9.110-3+deb9u5 (2018-09-30)