Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 am going to have my LPI 102 exam Saturday. I am confused about insmod and modprobe . I find some of threads said that modprobe execute insmod and load the required modules automatically. Is it right? And when should insmod and modprobe use files like /etc/modules.conf , /etc/modprobe.conf and the path MODPATH,MODULECONF?
I believe that the difference is that modprobe will cause a kernel module to be loaded from the installed kernel from the /lib/modules directory, whereas insmod will load any particular .ko file you point it at, whether in /lib/modules or not. insmod, combined with rmmod, is useful when working on a module; allowing you to recompile just the module and test it, without having to do a whole kernel compile, or hack at your /lib/modules files, potentially making your kernel unbootable.
When I see some things that use "insmod" they all seem to give the full path name to the module, while modprobe just has the name of the module without the ".ko". Oh, yeah, and modprobe will complain about dependencies!