| 1 |
On 12/12/05, Grant <emailgrant@×××××.com> wrote: |
| 2 |
> I'm still trying to figure out what exactly coldplug does. Is it a |
| 3 |
> replacement for /etc/modules.autoload.d ? |
| 4 |
|
| 5 |
Coldplug scans system busses, looking for hardware, and attempting to |
| 6 |
load any modules available for that hardware. It does this by running |
| 7 |
the scripts /etc/hotplug/*.rc. |
| 8 |
|
| 9 |
So for example /etc/hotplug/pci.rc scans /sys/bus/pci/devices, looking |
| 10 |
for devices. For each device it finds, it looks at |
| 11 |
/lib/modules/`uname -r`/modules.pcimap to see if there is a module |
| 12 |
available for that device. If there is, the script tries to load it. |
| 13 |
|
| 14 |
So yes, there is some overlap with /etc/modules.autoload.d/, because |
| 15 |
you can load these drivers there. The difference is that coldplug is |
| 16 |
limited to just hardware device drivers. Other drivers (like security |
| 17 |
drivers, io schedulers, or power management drivers) cannot be loaded |
| 18 |
this way, so you have to use the modules.autoload.d/ method. |
| 19 |
|
| 20 |
-Richard |
| 21 |
|
| 22 |
-- |
| 23 |
gentoo-user@g.o mailing list |
Archives