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've recently compiled 220.127.116.11 and it works flawlessly. I need to load some modules during boot but I don't have /etc/rc.d/rc.modules-18.104.22.168, do I need to create one? If so, what's the best way to do this? Or, can I load modules somewhere else?
Just remember, if you use the rc.local file, it is apparently the first and ONLY modules file that will be checked, so be sure everything you need is in there.
I have had good success keeping ONE rc.modules file for each kernel-version I happen to be using/testing, and using a symlink called rc.modules to point to the correct modules file to be used at the moment.
Lately all my kernels are 2.6.x.x, so I have named the modules file rc.modules-2.6.x.x, and I created a symlink called rc.modules, which points to it.
Assuming they are related enough (and they are), you might wanna start with the rc.modules-2.6.x from one of the Slackware 2.6.x kernels, fix whatever you need to, rename it to match your kernel, and symlink rc.modules to it. If not, then I guess you'll have to write it from scratch.
Last edited by H_TeXMeX_H; 02-05-2007 at 06:15 PM.
Have a look at your /etc/rc.M file. This loads things on startup in multi-user mode (the normal mode). The services you want should be identified by rc.[ service ] scripts which are set to executable if they are to be run. The printing module (parport_pc, lp, etc.), usb modules (ohci_hcd, sg, usb_storage, etc.), and sound modules (snd_*) are among those that are not started there. The firewall (iptables) modules are also not loaded there. Generally, any script in the rc.d directory that is executable will be run at startup. Your kernel may have automatic module loading and unloading as well, in which case the modules will be loaded when a need is detected. You can put module parameters in /etc/modprobe.conf.
There are so many possible variations that it really requires that you become familiar with your hardware and program needs. Run /sbin/lsmod to see what you have and then read up on what you need or think you need.
# This loads any kernel modules that are needed. These might be required to
# use your ethernet card, sound card, or other optional hardware.
# 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.
if [ -x /etc/rc.d/rc.modules.local -a -r /proc/modules ]; then
echo "Running /etc/rc.d/rc.modules.local:"
elif [ -x /etc/rc.d/rc.modules-$(uname -r) -a -r /proc/modules ]; then
echo "Running /etc/rc.d/rc.modules-$(uname -r):"
. /etc/rc.d/rc.modules-$(uname -r)
elif [ -x /etc/rc.d/rc.modules -a -r /proc/modules -a -L /etc/rc.d/rc.modules $
echo "Running /etc/rc.d/rc.modules -> $(readlink /etc/rc.d/rc.modules):"
elif [ -x /etc/rc.d/rc.modules -a -r /proc/modules ]; then
echo "Running /etc/rc.d/rc.modules:"
So the order of preference is rc.modules.local, rc.modules-`uname -r`, and finally rc.modules. The script even tells you if rc.modules is a symlink! The first one found is used, and the rest are ignored.
Edit: Clarification (For you non-Bashers out there)
The first on in the list found that is also executable is used.