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