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.
After compiling and installing kernel everything works nicely, but theres no modules loaded, what happens is when i log in as non root theres no module loaded, but then i go for instance iptables -L then that modules are loaded,
however im concerned about rc.modules, after installed custom kernel theres no rc.modules-188.8.131.52?
so my question is how do i load all modules in my customized kernel?
Well, I think that there should't be rc.modules created for your custom kernel. If you have installed Slack with test26 or huge26 kernel, then you should only link rc.modules with those kernel rc.modules. I.E.
# Priority is given first to a script named "rc.modules.local", then
# to "rc.modules-$FULL_KERNEL_VERSION", and finally to the plain "rc.modules".
# Note that if /etc/rc.d/rc.modules.local is found, then that will be the ONLY
# rc.modules script the machine will run, so make sure it has everything in
# it that you need.
Since rc.modules is called from rc.S, take a look in /etc/rc.d to see if you have an empty or wrong rc.modules.local.
@general failure very interesting link hopefully will help me.
ill play today with it.
rc.modules, is symlinked to other rc.modules-uname-r, the problem is that after custom installation rc.modules-184.108.40.206 wasnt created at all, thats why i asked if i need to create manually rc.modules-220.127.116.11, wich seems so!
Ill play with it today and will report after i finish,