From: Herve Eychenne <rv@wallfire.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Development <netfilter-devel@lists.netfilter.org>
Subject: Re: ERROR target in /proc/net/ip_tables_targets
Date: Thu, 25 Mar 2004 21:17:57 +0100 [thread overview]
Message-ID: <20040325201757.GN1115@eychenne.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0311270612230.30430@gw.localnet>
On Thu, Nov 27, 2003 at 06:20:06AM +0100, Patrick McHardy wrote:
> On Thu, 27 Nov 2003, Herve Eychenne wrote:
> > Yes, except than when you do a cat /proc/net/ip_tables_targets and
> > read "ERROR" at the end of the list, you get the strong (and
> > unpleasant) feeling that something went wrong and that the list may
> > not be complete (even if _you_ (netfilter developer) know it is).
> I never thought of it this way .. I actually had to laugh out about my
> ignorance not realizing what ERROR means to most people ;)
> > So (even if I understand your concerns at the time you wrote the
> > patch) this is IMHO not acceptable.
> > Please, let's not sacrifice "ignorant" user time and confidence for a
> > few duplicate lines of kernel code...
> Yes I totally understand your point, I'm going to fix it when I get
> around.
$ uname -a
Linux comet 2.6.4 #29 Thu Mar 18 19:42:39 CET 2004 i686 GNU/Linux
And it's still there. Is there patch? If yes, it has not been
submitted upstream...
Herve
--
_
(°= Hervé Eychenne
//)
v_/_ WallFire project: http://www.wallfire.org/
next prev parent reply other threads:[~2004-03-25 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 4:28 ERROR target in /proc/net/ip_tables_targets Herve Eychenne
2003-11-27 4:53 ` Patrick McHardy
2003-11-27 5:07 ` Herve Eychenne
2003-11-27 5:20 ` Patrick McHardy
2004-03-25 20:17 ` Herve Eychenne [this message]
2004-03-25 22:55 ` Patrick McHardy
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=20040325201757.GN1115@eychenne.org \
--to=rv@wallfire.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.