Nix wrote:
On 9 Apr 2006, Ville Herva yowled:
On Sun, Apr 09, 2006 at 05:44:16PM +0300, you [Ville Herva] wrote:
I just realized
# CONFIG_NETFILTER_XT_MATCH_STATE is not set
should probably be set. I'm building a new kernel now...
Ok, that seems to do it.
Thanks for the help, and sorry for the noise. I hope not too many people hit
the same glitch while upgrading...
I cetainly did. A simple `make oldconfig' ends up zapping pretty much
all the old iptables CONFIG_ options, so you end up with not much of
iptables or netfilter left.
I must admit not quite understanding why the xtables stuff is needed:
I thought that was needed for userspace connection tracking, which
while it sounds cool isn't something I'm using yet.
I think the root of the problem is that "make oldconfig" doesn't give
any warning when options are removed. So there's no warning that
iptables is gone, because the help for the new options doesn't tell you
"replaces XXXX" even if you as for help.
Suggestion: how hard would it be to have some extra value like y/n/m
which says print the help even though the option is gone? That would be
a reasonable thing to do for a version or two after things go away, and
certainly lower cost than having testers ask questions, rebuild kernels,
or just go away mad.
-
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]
