On Thu, 2 May 2002 10:49:41 -0400 (EDT),
Tom Oehser <email@example.com> wrote:
>Changing all =m to =n in my config makes a 4K difference in the kernel size.
>But, the kernel compiled with them off still seems to load the modules fine.
>Why is there such a size difference in the static part and what do I risk if
>I mix a kernel compiled with the modules off with said modules? What stuff
>is actually being compiled into the static part because of the modules I
>choose? Doesn't it defeat the point of modules to have dependencies or even
>effects on the static part caused by the choice of module compilation?
The majority of modules have no effect on kernel size but some modules
require base kernel code as well. This is typically common code or low
level setup functions. You will find that those modules will not load
now or will break.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:17 EST