No date in "uname -a" anymore
Hi all,
if I do this
~# uname -a
Linux squeeze 2.6.32-5-xen-amd64 #1 SMP Mon Feb 25 02:51:39 UTC 2013
x86_64 GNU/Linux
~# ls -l /boot/vm*
-rw-r--r-- 1 root root 2482528 May 10 15:32 /boot/vmlinuz-2.6.32-5-xen-amd64
~#
on a machine running squeeze, it is trivially easy to see that it
doesn't run the installed kernel, just by comparing the dates. The
machine hasn't been rebooted since the last update of the kernel package.
On wheezy this is a different matter:
~# uname -a
Linux wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux
~# ls -l /boot/vm*
-rw-r--r-- 1 root root 2833376 May 15 23:58 /boot/vmlinuz-3.2.0-4-amd64
~#
There is no date in the uname output anymore, which I could compare to
the kernel image file's timestamp.
Can someone please explain what exactly the "improvement" is in removing
information from uname's output?
<rant>
If I'd like to have taken away from me stuff of which others have
decided that I don't need it, I'd still use GNOME.
</rant>
And yes, I've seen
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694565#10
but
| The package version identifies what source was used and is thus a lot
| more useful than the build date.
doesn't sound convincing to me. As an administrator, I couldn't care
less what source was used to build the kernel package installed.
Oh, and what is nowadays the recommended method to determine whether or
not the machine is running the kernel from the latest package update?
--
Regards
mks
Reply to: