| View previous topic :: View next topic |
| Author |
Message |
chibi
n00b
Joined: 27 Nov 2005
Posts: 41
|
 Posted: Tue May 22, 2007 7:54 am Post subject: how to prevent udev autoloading modules at boot time? |
 |
|
is that possible?
it can only be added modules one by one in /etc/modprobe.d/blacklist |
|
| Back to top |
|
 |
mudrii
l33t
Joined: 26 Jun 2003
Posts: 789
Location: Singapore
|
| Posted: Tue May 22, 2007 8:08 am Post subject: |
|
|
you could try to recompile the kernel and eliminate the modules from the kernel
or to find the rules in udev rouls folder and comment the modules that you do not need
Check this link it may help you
http://gentoo-wiki.com/UDEV
_________________
www.gentoo.ro |
|
| Back to top |
|
|
chibi
n00b
Joined: 27 Nov 2005
Posts: 41
|
|
| Back to top |
|
|
VoVaN
l33t
Joined: 02 Jul 2003
Posts: 701
Location: The Netherlands
|
| Posted: Tue May 22, 2007 1:50 pm Post subject: |
|
|
| Look at /etc/modprobe.d/blacklist, maybe it helps. Keep us informed. |
|
| Back to top |
|
|
dch24
Tux's lil' helper
Joined: 15 Feb 2007
Posts: 99
|
| Posted: Wed Jul 11, 2007 11:02 pm Post subject: |
|
|
This post describes the difference between 'blacklist' and what you are trying to do:
| Joey Hess wrote: | Package: module-init-tools
Version: 3.3-pre11-1
Severity: normal
If you look up "module blacklist" or "modprobe blacklist" or "udev
blacklist" in google, the results are various and mostly wrong,
outdated, or distro-specific.
modprobe.conf(5)'s docuentation of the blacklist command is ok, but
still leaves open the question of how to really blacklist a module so
modprobe won't load it at all.
Expecting a regular user to read the documentation of the install
command and think of "install module /bin/true" as the way to turn off
loading of a module is probably expecting too much of many users. It's
even expecting too much of some developers; I did not make this
connection on my first or second reading of the man page, and did not
think of it until I saw it mentioned on the web[1].
Since module-init-tools has a FAQ, I thought it might help to document
how to blacklist a module there.
Something like:
| Code: | Q) How do I prevent udev or modprobe from loading a module?
A) Putting this in a file in /etc/modprobe.d/ will guarantee that modprobe
never loads a module (in this case the PC speaker driver), but it not
necessarily the best approach in all circumstances:
install pcspkr /bin/true
If there are two modules that can both support the same device, and
the wrong module is being used, the above won't help; it will prevent
the wrong module from being loaded, but will not load the correct
module. In this case, you should instead use the blacklist command:
blacklist eepro100
This will prevent the older eepro100 module from being used, and
allow the newer e100 module to be loaded instead.
See the modprobe.conf(5) man page for details. |
If you add this you might also want to add a pointer to it to
/etc/modprobe.d/blacklist
--
see shy jo
[1] http://www.beranger.org/index.php?page=3k&fullarticle=2256
Currently the 20th hit for "udev blacklist" |
In other words, this will disable it at the modprobe level. (Then when you want to use it, just add a # to comment out the line, and run update-modules and modprobe it in. Not exactly what you wanted, but ...)
There's a good discussion in the bug #130766 thread about using /etc/conf.d/rc to disable services (so the modules are still loaded but the service doesn't get started) and about the security hole opened by autoloading evbug. The bug is closed because "Comment #46 From Matthias Schwarzott 2007-02-13 00:16:10 0000 [reply] udev-104-r11 (and -r10) implement the wrapper-based blacklisting, by using the blacklist-lines from modprobe.conf" but I have not seen documentation or an example of how this works. |
|
| Back to top |
|
|
|
Kernel & Hardware
