Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Mercy Corps

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 157 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       Because  the modprobe command can add or remove extra more
       than one module, due to module  dependencies,  we  need  a
       method  of  specifying  what  options  are to be used with
       those modules.  modprobe.conf specifies those options,  as
       required.   It  can  also  be  used  to  create convenient
       aliases: alternate names for a module.   Finally,  it  can
       override  the  normal  modprobe  behavior  altogether, for
       those with very special requirements  (such  as  inserting
       more than one module).

       Note that module and alias names (like other module names)
       can have - or _ in them: both are interchangable  through­
       out all the module commands.

       The  format  of  modprobe.conf  is simple: one command per
       line, with blank lines and lines starting with  #  ignored
       (useful  for  adding  comments).   A  at the end of a line
       causes it to continue on the next line,  which  makes  the
       file a bit neater.

       The syntax is a simplification of modules.conf


       alias wildcard modulename
                 This  allows  you  to give alternate names for a
                 module.     For    example:    "alias     my-mod
                 really_long_modulename"  means you can use "mod­
                 probe    my-mod"    instead     of     "modprobe
                 really_long_modulename".    You   can  also  use
                 shell-style   wildcards,   so   "alias   my-mod*
                 really_long_modulename" means that "modprobe my-
                 mod-something" has the same effect.   You  can't
                 have  aliases  to  other  aliases (that way lies
                 madness), but aliases can  have  options,  which
                 will be added to any other options.

       options modulename option...
                 This  command  allows  you to add options to the
                 module modulename  (which  might  be  an  alias)
                 every  time  it  is  inserted  into  the kernel:
                 whether directly (using modprobe modulename,  or
                 because  the  module  being  inserted depends on
                 this module.

                 All options are added together:  they  can  come
                 from  an  option  for  the module itself, for an
                 install fred", which would do what  you  wanted.
                 Note  the --ignore-install, which stops the sec­
                 ond modprobe from re-running  the  same  install
                 command.  See also remove below.

                 You  can  also  use  install  to make up modules
                 which  don't  otherwise  exist.   For   example:
                 "install  probe-ethernet  /sbin/modprobe e100 ||
                 /sbin/modprobe eepro100", which will  try  first
                 the  e100 driver, then the eepro100 driver, when
                 you do "modprobe probe-ethernet".

       remove modulename command...
                 This is similar to the  install  command  above,
                 except  it is invoked when "modprobe -r" is run.
                 The removal counterparts  to  the  two  examples
                 above  would  be: "remove fred /sbin/modprobe -r
                 --ignore-remove fred && /sbin/modprobe  -r  bar­
                 ney",  and "remove probe-ethernet /sbin/modprobe
                 -r eepro100 || /sbin/modprobe -r e100".

       include filename
                 Using this command, you can include  other  con­
                 figuration  files, which is occasionally useful.
                 Note that aliases  in  the  included  file  will
                 override aliases previously declared in the cur­
                 rent file.

Backwards Compatibility

       There is a generate_modprobe.conf program which should  do
       a  reasonable  job  of  generating modprobe.conf from your
       current (2.4 or 2.2) modules setup.

       Although the syntax is  similar  to  the  older  /etc/mod­
       ules.conf, there are many features missing.  There are two
       reasons for this: firstly, install and remove commands can
       do  just  about  anything,  and secondly, the module-init-
       tools modprobe is designed to be simple enough that it can
       be easily replaced.

       With  the complexity of actual module insertion reduced to
       three system calls (open, read, init_module), and the mod­
       ules.dep file being simple and open, producing a more pow­
       erful modprobe variant can be done independently if  there
       is a need.

Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can get all the latest Site and Linux news by checking out our news page.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds