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.
I have a problem with Salix, and already asked on their forum without gettings an answer yet. Since Salix is based on Slackware I think this could be related to Slackware, too.
On the console between issue and the login prompt I always get the message "Hint: Num Lock on".
Where does this message come from, and is it possible to deactivate this message?
On a notebook it can be quite helpful, even if there's a num lock indicator light, too, but on a desktop I don't like it too much, because the numeric keypad is separated and the num lock indicator light is seen a lot better.
Sorry for necrobumping this thread, but another (perhaps more practical) solution is to use setleds to turn numlock on/off as you login/logout. Great for people who like to keep numlock on.
# Turn on numlock:
if [ -z "$DISPLAY" ]; then
setleds +num > /dev/null 2>&1
# Turn off numlock:
if [ -z "$DISPLAY" ]; then
setleds -num > /dev/null 2>&1
This was not the problem. The problem was the message which was always printed by agetty, when numlock was turned on. The question was not how to turn numlock on or off. And it was not a bash, but an agetty issue.
Please do not assume that the entire community of the internet is here at your personal service. You lost the sole ownership to the text contained in your post the moment you clicked 'submit thread/reply', from there on enabling anyone on the internet to read your post and make use of the information contained within it.
My solution, while somewhat alternative, is not irrelevant to the issue, and I do believe anyone with a positive attitude (read: who is not a troll) and who do not just simply have their minds irrationally and obsessively set on modifying the behaviour of agetty itself instead of just as well working around the issue, will be able to see just how it can be useful to them.
That said, I do not intend to post any further replies as I have concluded that you are indeed a troll. I can only hope that you learn something from what I just wrote, although I realize I may be overly optimistic.
Question is: Who is the troll? The one who opened a thread with a very specific question, and who posted the solution to this question? Or the one who posted a solution to a completely different problem in this thread after the issue was already solved, and tells something about the owner of the internet?
I have no idea what is going on in this thread. The solution posted by the OP did, indeed, solve the posted problem and was confirmed. So, if you are a Salix user and do not wish to see the num lock message, post #4 is the post for you!
The other fix posted would have solved a slightly different issue that wasn't posted but is also useful to know for people that find that sort of knowledge useful.
Still don't know why the argument, but hey, I'm not the one with a num lock obsession either.....