Anton Aylward wrote:
Somewhere here I have a server running Mandriva that says
2.6.39.4-5.1-generic #1 SMP Wed Jan 4 13:50:55 UTC 2012 i686
Note the date: Long past the spring 2011 'renaming'.
That date is the build date.
But lets not forget that the strings returned by 'uname' can be whatever you want. When you rebuild the kernel and determine what goes in there you can set those strings to whatever your sweet heart desires; there's no magic that automatically updates it in sequence - that why other distributions can modify it with their own tags.
The regular tools (e.g. menuconfig) will let you modify the "5.1-generic" string (with CONFIG_LOCALVERSION), but not the kernel version.
No, what I'm asking is this. Forget what uname says. If I don't have source how can I find out if the kernel I'm running on a particular machine, the drivers, schedulers memory allocators etc are from what real level of revision? With some degree of granularity.
What's wrong with uname? If you want to look at modules, "modinfo <module>" will tell you the most pertinent stuff.
For example, I've held off upgrading my various Suse machines from 11.4 to 12.1 because of the problems reported with systemd, but the other machines here running systemd under fedora and mandriva don't have any of the problems that were reported with the opensuse 12.1 implementation. That bothers me; what code was really being run?
I think it's not really _systemd_ itself, but rather our integration of it that's been causing problems for us. BTW, 12.1 works very well with sysvinit, and 12.1+updates is pretty good with systemd too. -- Per Jessen, Zürich (27.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org