localmodconfig

Posted Aug 24, 2009 2:19 UTC (Mon) by ABCD (subscriber, #53650)
In reply to: localmodconfig by mjg59
Parent article: In brief

> Anything that's loaded at boot is probably still loaded.

That usually isn't true in the special case of the microcode module, as the various distribution's init scripts generally load the module, update the microcode, then immediately explicitly unload the module.

localmodconfig

Posted Aug 24, 2009 14:21 UTC (Mon) by nevets (subscriber, #11875) [Link] (2 responses)

If there's a way to know about these, then certainly let me know. Email me at rostedt@goodmis.org. The localmodconfig is a start. But if we are missing necessary modules to boot the kernel, then we need to find a way to fix that.

localmodconfig

Posted Aug 25, 2009 1:35 UTC (Tue) by dirtyepic (guest, #30178) [Link]

that's the only one i can think of. i was mistaken about the cpufreq stuff of course. :) nice job, btw, this is something that was sorely needed.

localmodconfig

Posted Sep 22, 2009 19:49 UTC (Tue) by BobRobertson (guest, #2048) [Link]

I found out about this after posting a "wish list" to lxer.com which
included building a kernel .config that had only the actually used modules
compiled in, and everything else as loadable modules.

I'll add my own Thank You to the list.