Peter Peltonen wrote:
> Umm, about that 'make dep', what does it actually do?
[warning: armchair expert making stuff up]
The kernel is full of lots of code that only gets referenced if it's
needed. Whenever you change any of the config parameters (as listed in
the top-level .config file, which is written by the various 'make
*config' operations), 'make dep' runs through the source tree and
rewrites any necessary Makefiles so that make will give gcc the right
list of files to compile, and any special arguments that need to be
passed on (for example, is this code to be linked straight to the kernel
or left standing as a module).
During the actual compilation process, 'make' gets called within the
subdirectory for each component of the kernel. If the Makefile hasn't
been "turned on" by a previous run of the depend command, you'll see one
of those "Nothing to do for..." messages during compile, and we move on
to the next task if there is one.
> Somewhere I read I should always do 'make dep' after modifying modules.conf
This confuses me. /etc/modules.conf? That only cares about modules you
have compiled and installed. It doesn't have any idea what's going on
in the kernel source, and will be quite happy on a machine that doesn't
have kernel source installed.
> and from that I thought that it would check if I have the modules listed there
> loaded, but no. I had to reboot my machine to get the modules in modules.conf
> to be loaded (or use insmod).
"depmod -a" may remove the need for a reboot, provided that all you've
changed are the modules.conf file and the set of modules installed under
the currently-active tree.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
