SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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...
-------------------------
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...)
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
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 )
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.