CONFIG_KMOD in x86_64/defconfig (was Re: iptables is complaining with bogus unknown error 18446744073709551615)

[Harald Welte <laforge@netfilter.org>]

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]

On Thu, Apr 27, 2006 at 11:41:40AM -0400, Maurice Volaski wrote:
> >On Wed, Apr 26, 2006 at 09:12:38PM -0400, Maurice Volaski wrote:
> >> Automatic kernel module loading! That is an option and it's off by
> >> default. When it's off, attempts to load kernel modules are ignored
> >> internally, and that's why iptables was failing. It tried to load
> >> xt_tcpudp, but was ignored by the kernel.
> >What do you mean by "it's an option" and "is off by default".  I would
> >claim that any major linux distribution that I've seen in the last ten
> >years has support for module auto loading (enabled by default).
> 
> Distribution vendors are free to change it to whatever they want, I guess, but it's OFF by 
> default in the official kernel (.config).

apparently architecture-specific:

grep KMOD arch/i386/defconfig
CONFIG_KMOD=y

grep KMOD arch/x86_64/defconfig
CONFIG_KMOD is not set

don't know why x86_64 turns it off by default.  the help message says
'if unsure, say Y' (which makes sense!)
-- 
- Harald Welte <laforge@netfilter.org>                 http://netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]