From: Bill Davidsen <davidsen@tmr.com>
To: Nix <nix@esperi.org.uk>
Cc: Patrick McHardy <kaber@trash.net>,
linux-kernel@vger.kernel.org, netfilter@lists.netfilter.org,
davem@davemloft.net
Subject: Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter
Date: Tue, 11 Apr 2006 15:10:02 -0400 [thread overview]
Message-ID: <443BFF0A.7050303@tmr.com> (raw)
In-Reply-To: <87psjqg2nt.fsf@hades.wkstn.nix>
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.
prev parent reply other threads:[~2006-04-11 21:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060403180207.E849EE007A12@knarzkiste.dyndns.org>
2006-04-03 3:47 ` Linux 2.6.17-rc1 Linus Torvalds
2006-04-03 5:13 ` KAMEZAWA Hiroyuki
2006-04-03 7:38 ` Russell King
2006-04-03 11:18 ` Michael Schierl
2006-04-03 19:47 ` Russell King
2006-04-03 21:48 ` Greg KH
2006-04-06 14:27 ` Martin Michlmayr
2006-04-06 21:21 ` Michael Schierl
2006-04-03 13:33 ` Jim MacBaine
2006-04-03 16:24 ` Tomasz Torcz
[not found] ` <20060403191552.GA8568@kroah.com>
2006-04-04 6:50 ` Tomasz Torcz
2006-04-03 19:09 ` Ralf Hildebrandt
2006-04-04 3:25 ` Andrew Morton
2006-04-04 8:05 ` Ralf Hildebrandt
2006-04-04 8:44 ` Andrew Morton
2006-04-09 11:28 ` Ralf Hildebrandt
2006-04-08 21:10 ` Hans-Peter Jansen
2006-04-04 23:39 ` [FUN]Re: " Ingo Oeser
2006-04-08 20:09 ` Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter Ville Herva
2006-04-08 22:05 ` David S. Miller
2006-04-09 4:09 ` Patrick McHardy
2006-04-09 7:43 ` Ville Herva
2006-04-09 14:44 ` Ville Herva
2006-04-09 14:45 ` Ville Herva
2006-04-09 16:00 ` Nix
2006-04-09 16:23 ` Andre Tomt
2006-04-11 11:27 ` Jan Engelhardt
2006-04-09 16:37 ` Patrick McHardy
2006-04-09 16:53 ` Nix
2006-04-09 17:10 ` Ville Herva
2006-04-11 9:03 ` Harald Welte
2006-04-11 19:10 ` Bill Davidsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=443BFF0A.7050303@tmr.com \
--to=davidsen@tmr.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter@lists.netfilter.org \
--cc=nix@esperi.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox