On Fri, 21 Aug 2009, Ingo Molnar wrote: > > OK, I'll add that to my todo list. Note, it the local config is > > only as good as the starting .config. That is, it never touches =y > > settings, because it only uses loaded modules as a base. Thus if > > something is set to =y it will always be set to =y. > > > > What would you have in mind. Just randomly enabling modules? If we > > enable a "y" config then the next local*config will still keep > > that set. > > Why - isnt local*config picking up environmental (currently running > kernel) properties? I.e. it would always set those things that are > needed - and randomize the rest. Have i misunderstood how it works? Yes, this is a simple script. The only thing it does to find out what is configured is run "lsmod". Others have tried (in vain) to be able to look into things like lspci and lsusb to figure out what options to enable, just to end up with something so complex that it doesn't work. It truly would be great to be able to have something examine the box and be able to enable everything that it finds. But that is not what I set out to do. I only wanted to disable the hundreds of modules that a distro gives us so I can have a streamed line config that will boot my system and build in a decent time. I've been using this script since 2005 and it has worked out great. I even posted it after I first wrote it: http://lkml.org/lkml/2005/3/11/39 This seems to be a very useful tool. I don't want to prevent it from going further because we try to make it do too much. Lets get what we have now in, and then we can look at alternatives. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
