Red HatThis forum is for the discussion of Red Hat Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Has anyone seen a decent HOWTO regarding /etc/modules.conf? The man page is not clear to a non-programmer like me. I'm looking for an understandable explanation of the formatting.
In most cases the modules.conf will tell what modules to load at boot time in which most cases its the modprobe command then the module name.
But since its executable though and read like a script in a way, then you can do basic shell scripting in the file, depending on what your trying to achieve though in loading your module, it all really depends on the module.
Not much else to that file really. At least I don't think there is or I've never had any other reason for it to be.
I find nothing explanatory about /etc/modules.conf in the kernel modules HOWTO. The man page of modules.conf is written to document how it works (from a programmers' perspective, it appears), but not _how_ to use it. It appears to offer great flexibility, but what I want to know is how that can be accomplished.
In other words, the existing documentation describes the tools; I want to know how to use them.
I think the question people might be asking is: Why do you want to mess with it? In other words, what is it you think changing /etc/modules.conf might do for you? Generally speaking, the stock modules.conf works for most stuff, and for special situations, there's usually documentation saying "add these three lines to /etc/modules.conf". You say you're a non-programmer. That suggests to me that you'll generally be running pretty standard programs, or one hopes, well-documented non-standard programs.
I deal with a number of poorly-documented programs all the time (I have yet to see a really well-documented one).
Obviously the tools are there, the capabilities of /etc/modules.conf are more than what is commonly used, but where's the documentation on how to use them? That's all I'm asking; I'm not looking for anything specific at the present time. When the documentation for aome app says "add these three lines to /etc/modules.conf", how did they arrive at that solution? Why are there more capabilites to modules.conf that anyone ever seems to use? What would you use them for?
I've looked for answers to those questions and haven't found any.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.