Login reports wrong kernel
 

Here is an odd one:

I run the 2.6.9 kernel on Slackware-Current, but when I login I get:


Last login: Sat Nov 27 18:32:17 2004 from 192.168.0.101
Linux 2.4.26.


It's just odd that it reports the wrong kernel version... any work around/fix?
(BTW: I'm logging in from Windows via SSH)

what does it show when you type this in.......??

Ignore what 320mb said, that just basically tells you what uname -a will display and its probably correct on your current version.

Edit your /etc/motd to reflect the correct kernel version in which any person who's been using Slackware for quite some time will know that the base default Slackware install puts the kernel version as the motd (message of the day) and should have known this by the information you've provided... ;)

I know about editing the motd ;), but shouldn't it update automatically? It's certainly not an issue, just curious.

I have never edited /etc/motd and mine currently says 2.6.9, which is correct. Looks like it is automatically updated.

Did you make changes to lilo.conf to point to your new kernel? Just a thought.....

from: http://channels.lockergnome.com/linu...motd_tip.phtml

-------------------------
It turns out Slackware resets the contents of the MOTD file during shutdown. When you shut down or reboot, the /etc/rc.d/rc.S file is executed. In this file, you'll find the following bit of script:

echo "$(/bin/uname -sr)." > /etc/motd

In English? Run the command uname -sr (which, in my case, produces "Linux 2.4.26") and echo the results followed by a period. The right angle bracket directs the output to the file /etc/motd. Since it's a single bracket, it replaces the file with -- again, in my case -- "Linux 2.4.26."

Incidentally, if this line had two angle brackets -- >> -- it would append the echoed output, and the /etc/motd file would get one line longer with each reboot.

So how do you fix it? Easy. Just comment the line with a hash (#). This turns the line into a comment ignored by the shell, so the command will not be run, and your /etc/motd file will make it through the shutdown process unscathed.
------------------

so , at shutdown the " uname -r " -output is written to " motd ".
my Q. : are you really running 2.6.9 ? ( then a reboot might help...)

egag

Last login: Sun Nov 28 00:29:36 2004 from 192.168.0.101
Linux 2.4.26.
umdarby@slackbox:~$ uname -a
Linux slackbox 2.6.9 #4 SMP Sun Nov 14 12:57:36 EST 2004 i686 unknown unknown GNU/Linux
mdarby@slackbox:~$



lol, yeah, I'm running 2.6.9.

It seems as though the "echo "$(/bin/uname -sr)." > /etc/motd" line is commented out by default. I uncommented and ran the echo code and all is well ;)

maybe in -current. in my rc.S ( Slack10 ) it's not commented out and i didn't change it .
whatever.....we know how to edit a line... :)

egag

yeah, it must only be -current. I've never had to edit that line; eh oh well ;)

Thanks for your help

mislead by this:
-------------
It turns out Slackware resets the contents of the MOTD file during shutdown. When you shut down or reboot, the /etc/rc.d/rc.S file is executed.
-------------

rc.S is executed at boot.
( so what i first wrote here was crap ) :)

egag