[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

/etc/modules vs. kmod/modules.conf



hey all,
just a general question... i usually build my kernels with modules for
everything, just like the debian kernel. it's still one kernel per
machine, and the few modules i compile are still always loaded, so i
don't know why i do so, but i guess it doesn't really matter.

however, i have a question: take, for instance, an ethernet card
(let's assume a tulip). i can either add 'alias eth0 tulip' to
/etc/modutils/aliases and run `update-modules`, or i can add 'tulip' to
/etc/modules. in the end, it doesn't matter. the first method makes
sure that when /etc/init.d/networking calls ifconfig (or the if-up
wrapper), the tulip.o module is loaded via modprobe since eth0 is
needed. in the second case, tulip.o is loaded immediately before going
through the rc?.d directory.

what is the preferred method of loading modules? i guess /etc/modules
will be the answer because of tool like modconf, but i don't generally
use debian kernels or modconf, so i am interested on what you have to
say.

martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck
-- 
"the human brain is like an enormous fish --
 it is flat and slimy
 and has gills through which it can see."
                                                       -- monty python

Attachment: pgpublW9r8ZyI.pgp
Description: PGP signature


Reply to: