From: Patrick McHardy <kaber@trash.net>
To: Phil Oester <kernel@linuxace.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [iptables 1.3.0 / libiptc patch] sort chains by hooknum/names
Date: Fri, 04 Mar 2005 23:38:23 +0100 [thread overview]
Message-ID: <4228E35F.4010609@trash.net> (raw)
In-Reply-To: <20050304220827.GA23938@linuxace.com>
Phil Oester wrote:
> On Fri, Mar 04, 2005 at 09:21:14PM +0100, Olaf Rempel wrote:
>>
>>I've created two patches to revert it to the "old" behavior:
>>first buildin chains, sorted by hooknum, than userdefined chains, sorted by name.
>
> Why is the old behaviour better than the current? Any scripts you have
> should be smart enough to check for '^Chain ______' to determine chain.
Unfortunately not all are, so best chance of no breakage is keeping the
old behaviour. I can't remember where, but someone already reported a
broken script because of this change.
Regards
Patrick
next prev parent reply other threads:[~2005-03-04 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 20:21 [iptables 1.3.0 / libiptc patch] sort chains by hooknum/names Olaf Rempel
2005-03-04 22:08 ` Phil Oester
2005-03-04 22:38 ` Patrick McHardy [this message]
2005-03-04 23:15 ` Olaf Rempel
2005-03-04 23:04 ` Patrick McHardy
2005-04-19 14:51 ` Jonas Berlin
2005-03-05 2:07 ` Herve Eychenne
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=4228E35F.4010609@trash.net \
--to=kaber@trash.net \
--cc=kernel@linuxace.com \
--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.