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 run a 24/7 server on my Slackware 10.2 box. It was running kernel 2.6.13 kernel for 3 months. This weekend I realized that when it boots it would boot normally and then a weird message went by that said:
and had a bunch of strange numbers below it. I didn't used to get this and it worried me. I compiled kernel 2.4.32 and now when I boot with that kernel I don't get the funny start up message.
What appeared right before it in log? I guess some program crashed on startup, leaving inner function call trace. It is information inner to program (and useful for debugging/bug reporting sometimes), but it can be interesting for you which program crashed. Or ignore it - if you are OK with 2.4... For some time, until you will upgrade..
My wireless NIC module is kernel specific and I had to uninstall it from the 2.6.13 kernel in order to get it to work in the 2.4.32 kernel. I was also worried that somebody had cracked into my server and made it into a sleeping zombie-that kernel has no NIC now...anyway, I will boot into the 2.6.13 kernel when I get home and post the relevant part of dmesg.