| 1 |
On Fri, Jan 25, 2013 at 1:24 PM, Nuno J. Silva <nunojsilva@×××××××.pt> wrote: |
| 2 |
> Is there any syntax to check if something is either disabled or built as |
| 3 |
> a module? |
| 4 |
|
| 5 |
Very problematic. What is built in for the currently running kernel |
| 6 |
can be fairly reliably determined by grepping /proc/config.gz - IF |
| 7 |
support for that was enabled in the kernel. But, there is no |
| 8 |
guarantee that this kernel will be running on the next boot. |
| 9 |
Determining what is build as a module really requires interpreting the |
| 10 |
contents of /lib/modules - a module could have been built after the |
| 11 |
kernel was built, in which case /proc/config.gz might indicate no |
| 12 |
support even though it is supported. I don't think DEVTMPFS can be |
| 13 |
made a module, however (not sure on that). |
| 14 |
|
| 15 |
You can also check /usr/src/linux/.config, but the sources might not |
| 16 |
correspond to the running kernel, or the kernel on the next reboot, or |
| 17 |
whatever. |
| 18 |
|
| 19 |
It really is a touchy situation, hence all the emails in the thread. |
| 20 |
You can build something that will work OK 80% of the time though by |
| 21 |
checking the source tree. |
| 22 |
|
| 23 |
Part of me wonders if we should just ship a binary kernel/initramfs as |
| 24 |
an option. Then again, users could just use genkernel and get |
| 25 |
something like that anyway. My main issue with genkernel is that its |
| 26 |
default options are focused more on the install CD than ordinary use - |
| 27 |
things like tuners/multimedia/lirc and the like tend to not be |
| 28 |
enabled. I would think a typical desktop-oriented distro is going to |
| 29 |
enable as a module anything that doesn't cause breakage. |
| 30 |
|
| 31 |
Rich |
Archives