Messages in this thread | | | Date | Thu, 2 May 2002 10:49:41 -0400 (EDT) | From | Tom Oehser <> | Subject | module choices affecting base kernel size??? |
| |
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?
-Tom
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |