[BusyBox 0001401]: install option in modprobe.conf doesn't work

bugs at busybox.net bugs at busybox.net
Fri Jun 22 11:48:42 UTC 2007


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1401 
====================================================================== 
Reported By:                quitte
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   1401
Category:                   Kernel Module Support
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             06-21-2007 18:54 PDT
Last Modified:              06-22-2007 04:48 PDT
====================================================================== 
Summary:                    install option in modprobe.conf doesn't work
Description: 
The install and remove options in modprobe.conf do not work at all. The
--ignore-install option is missing,too.
from the modprobe.conf manpage:
install modulename command...
                 This  is  the  most powerful primitive in modprobe.conf:
it tells modprobe to run your command
                 instead of inserting the module in the kernel as normal. 
The command can be  any  shell  com&http://busybox.net/bugs/view.php?id=8208;
                 mand:  this  allows  you to do any kind of complex
processing you might wish.  For example, if
                 the module "fred" worked better with the module "barney" 
already  installed  (but  it  didn’t
                 depend on it, so modprobe won’t automatically load it),
you could say "install fred /sbin/mod&http://busybox.net/bugs/view.php?id=8208;
                 probe barney; /sbin/modprobe --ignore-install fred",
which would do what you wanted.  Note the
                 --ignore-install,  which  stops  the second 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".

====================================================================== 

---------------------------------------------------------------------- 
 vda - 06-22-07 04:48  
---------------------------------------------------------------------- 
> For example, if the module "fred" worked better with the module "barney"
already installed...

...you have to mail lkml and help kernel people to improve "fred" to not
need to jump thru the hoops like this.

It's not a bug. It's a "missing feature which exists in standard
modprobe". I am not convinced yet we want to turn busybox modprobe into
generic application launcher by having this peculiar option.

Please explain why do you need that. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-21-07 18:54  quitte         New Issue                                    
06-21-07 18:54  quitte         Status                   new => assigned     
06-21-07 18:54  quitte         Assigned To               => BusyBox         
06-21-07 19:02  quitte         Issue Monitored: quitte                      
06-22-07 04:48  vda            Note Added: 0002498                          
======================================================================




More information about the busybox-cvs mailing list