All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herve Eychenne <rv@wallfire.org>
To: Olaf Rempel <razzor@kopf-tisch.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [iptables 1.3.0 / libiptc patch] sort chains by hooknum/names
Date: Sat, 5 Mar 2005 03:07:25 +0100	[thread overview]
Message-ID: <20050305020725.GC30982@eychenne.org> (raw)
In-Reply-To: <20050304212114.130e2a7c@coruscant>

On Fri, Mar 04, 2005 at 09:21:14PM +0100, Olaf Rempel wrote:

> hi list

> >From 1.3.0 all chain names were alphabetically sorted when listing tables.
> A user-defined chain 'AAA' is listed before the buildin chain "INPUT", and 
> "FORWARD" is listed before "INPUT".

> I've created two patches to revert it to the "old" behavior:
> first buildin chains, sorted by hooknum, than userdefined chains, sorted by name.

Appart from the fact that it restores the old behavior (and avoids
breakage of some badly written scripts or apps), can you give a
single reason why the listing should be sorted?

Why not sort the output of a lot of commands (like lsof, netstat, ps,
etc.) then?  Hint: probably because there is no interest in wasting CPU
time for this.

 Herve

-- 
 _
(°=  Hervé Eychenne
//)
v_/_ WallFire project:  http://www.wallfire.org/

      parent reply	other threads:[~2005-03-05  2:07 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
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 [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=20050305020725.GC30982@eychenne.org \
    --to=rv@wallfire.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=razzor@kopf-tisch.de \
    /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.