Messages in this thread | | | Subject | Re: CONFIG_KMOD in x86_64/defconfig (was Re: iptables is complaining with bogus unknown error 18446744073709551615) | From | Arjan van de Ven <> | Date | Thu, 27 Apr 2006 22:01:57 +0200 |
| |
On Thu, 2006-04-27 at 16:24 -0300, Harald Welte wrote: > 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!)
also defconfig is really irrelevant... you should look at what the Kconfig has to say
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |