> I did, and it is -- but that's not the point. OK, so ifconfig is
> compiled to look for those protocols. But I've explicitly configured
> my kernel to _exclude_ those protocols.
No you didn't. You configured your kernel not to include them. It's only going
looking for them when an application (ifconfig) explicitly asks to use them.
In the same way, if a userspace program attempts to access an absent character
or block device, the kernel will ask kmod to provide it.
> Yet kmod insists on spawning a modprobe for each one, even though I've told
> it not to support those protocols in any way.
The way things stand ATM, it's possible to compile modules later and simply
add them to your module directory, and kmod will auto-load them.
This is, IMO, a Good Thing, because it means that I can compile extra modules
when I get new hardware or need new functionality, without having to recompile
the whole kernel every time.
If you don't want your kernel to attempt to load modules for things that it
doesn't have when userspace asks to use them, then disable kmod. If you want
to disable only certain modules, then alias them to 'off' in /etc/conf.modules
---- ---- ----
David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/