exporting symbols in kernel only when a module is compiled?

exporting symbols in kernel only when a module is compiled?

[Shaya Potter]

Ok, I'm sure this isn't limited to tcp_hashinfo, but does it make sense
to only export some symbols if "x" module is compiled into the kernel?  

For example with tcp_hashinfo, its only exported if ipv6 is compiled as
a module.  So if one statically compiles in ipv6 or doesnt compile it at
all, its not available to any other modules.  Is there a good reason for
it here?  Are there other similiar situations with other symbols? 
Should it be this way?  

It's possible to get around with recompiling modules and System.map
hackery, but should it be necessary?

thanks,

shaya

Re: exporting symbols in kernel only when a module is compiled?

[Kasper Dupont]

Shaya Potter wrote:
> 
> So if one statically compiles in ipv6 or doesnt compile it at
> all, its not available to any other modules.

I think the major problem here is, that if you at first doesn't
compile ipv6 at all, and later want to compile it as a module,
it will not work. I think it would be better if choosing a
feature as module or not compiled at all doesn't change anything
in the kernel.

-- 
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:aaarep@daimi.au.dk
or mailto:mcxumhvenwblvtl@skrammel.yaboo.dk