SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Slackware 14 (Server),Suse 13.1 (Desktop),, Mepis on the wifes lappy
uname -a gives wrong info
Have just upgraded my kernel to 2.6.10 and my box fired up faultelssly first time, but, as a check, I issued the command uname -a, and it tells me that I am still using 2.6.7. Now as I have physically moved my 2.6.7 kernel from where it normally resides, I canīt quite figure out why this is. I use grub as a bootloader, so no answers please telling me to re-run lilo.
So where does uname get itīs info from? is it from withing the kernel itself, or from within the /etc/motd file (which would explain it.
It's a shot in the dark but go back to the kernel source tree and take a peek at the Makefile, it shows the version numbers in there, see if there set to 2.6.10.. lol that would be funny if they were not.
Question, in your /lib directory is there a 2.6.7 folder under modules? it could just be looking to see if that folder exists and if it does that's probly what it reports.
If uname says 2.6.7, then you're running 2.6.7. Also check `uname -v` to see the compile time for the kernel you're running. I believe uname gets the kernel information from the kernel.
I do not use grub, but don't you have to update it somehow when you upgrade the kernel just like you do with lilo? Have you done that? Did you copy the new kernel to /boot? I know, it's the stupid things, but they're easy to forget.
Anyone using grub want to fill us in on how to update it to use the new kernel.
I don't see anything in that thread about uname being based on the motd file, just about the motd file being wrong in some cases. It appears that uname returns the correct kernel version number (i.e. the one you're running).
Back to my theory that the thread starter is not actually running 2.6.10.