On Fri, 25 Jan 2013 13:47:05 -0500 Rich Freeman <ri...@gentoo.org> wrote:
> Very problematic. What is built in for the currently running kernel > can be fairly reliably determined by grepping /proc/config.gz - IF > support for that was enabled in the kernel. But, there is no > guarantee that this kernel will be running on the next boot. > Determining what is build as a module really requires interpreting the > contents of /lib/modules - a module could have been built after the > kernel was built, in which case /proc/config.gz might indicate no > support even though it is supported. I don't think DEVTMPFS can be > made a module, however (not sure on that). Surely even that isn’t good enough, since the user could have built an option as a module, tested it out, discovered it worked fine, and then rebuilt the kernel with the option set to Y, but the .ko file would still be left lying around? Chris
