On Tue, Feb 21, 2006 at 02:17:32AM +0100, Patrick McHardy wrote:
>
> Arnaldo apparently wants to fix it differently, but maybe you could help
> us with conntrack :) CONFIG_IP_NF_CONNTRACK and CONFIG_NF_CONNTRACK
> should be mutually exclusive. Specifying
>
> CONFIG_IP_NF_CONNTRACK
> depends on CONFIG_NF_CONNTRACK=n
>
> CONFIG_NF_CONNTRACK
> depends on CONFIG_IP_NF_CONNTRACK=n
>
> will avoid asking for NF_CONNTRACK when IP_NF_CONNTRACK is set, but not
> the other way around.
Even worse, kconfig will complain about a circular dependency.
CONFIG_IP_NF_CONNTRACK
CONFIG_NF_CONNTRACK
depends on CONFIG_IP_NF_CONNTRACK=n
CONFIG_IP_NF_CONNTRACK will be visible if CONFIG_NF_CONNTRACK is set,
but as soon as CONFIG_IP_NF_CONNTRACK is set, CONFIG_NF_CONNTRACK is
automatically set to n.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
