Provided by: module-init-tools_3.16-1ubuntu2_i386 bug


       depmod.conf, depmod.ddepmod.d — Configuration file/directory for depmod


       The  order  in which modules are processed by the depmod command can be
       altered on a global or per-module basis. This is  typically  useful  in
       cases  where  built-in  kernel modules are complemented by custom built
       versions of the same and the user wishes  to  affect  the  priority  of
       processing  in  order  to  override  the module version supplied by the

       The format of depmod.conf and  files  under  depmod.d  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.


       search subdirectory...
                 This  allows  you  to specify the order in which /lib/modules
                 (or other configured module location) subdirectories will  be
                 processed  by  depmod.  Directories are listed in order, with
                 the highest priority given to the first listed directory  and
                 the  lowest  priority given to the last directory listed. The
                 special  keyword  built-in  refers  to  the  standard  module
                 directories installed by the kernel.

                 By default, depmod will give a higher priority to a directory
                 with the  name  updates         using  this  built-in  search
                 string:  "updates built-in" but more complex arrangements are
                 possible and are used in several popular distributions.

       override modulename kernelversion modulesubdirectory
                 This command allows  you  to  override  which  version  of  a
                 specific  module  will  be  used  when  more  than one module
                 sharing the same name is processed by the depmod command.  It
                 is  possible to specify one kernel or all kernels using the *
                 wildcard.  modulesubdirectory is the name of the subdirectory
                 under  /lib/modules  (or  other  module  location)  where the
                 target module is installed.

                 For example, it is possible to override the  priority  of  an
                 updated  test  module called kmod by specifying the following
                 command: "override kmod * extra".  This will ensure that  any
                 matching  module  name installed under the extra subdirectory
                 within /lib/modules (or  other  module  location)  will  take
                 priority  over  any  likenamed module already provided by the


       This manual page Copyright 2006-2010, Jon Masters, Red Hat, Inc.