[lkml]   [2002]   [May]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectmodule 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?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.044 / U:0.048 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site