From: Ben Greear <greearb@candelatech.com>
To: David Miller <davem@davemloft.net>
Cc: billfink@mindspring.com, shemminger@vyatta.com,
diego@woitasen.com.ar, netdev@vger.kernel.org
Subject: Re: ip route show shows the routes in the inverse order?
Date: Tue, 13 Mar 2012 08:37:42 -0700 [thread overview]
Message-ID: <4F5F69C6.7000900@candelatech.com> (raw)
In-Reply-To: <20120312.235234.73408595516828250.davem@davemloft.net>
On 03/12/2012 11:52 PM, David Miller wrote:
> From: Bill Fink<billfink@mindspring.com>
> Date: Tue, 13 Mar 2012 02:15:29 -0400
>
>> Some scripts may depend on this plus its much more efficent that way
>> if trying to find a matching route since you can quit on the first
>> match instead of having to scan the entire routing table.
>
> No script should be doing stuff like this, let the tool do it for you
> via "ip route get ADDR"
>
> There is absolutely no argument for routes to be listed in one order
> or another, and anything depending upon order is extremely fragile
> and needs to be fixed up anyways.
The argument is ease of use by whatever human is reading the
information..but it could be done in the 'ip' tool.
Humans are fragile indeed, but it's often easier to fix the
computer than fix the humans.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-03-13 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 1:18 ip route show shows the routes in the inverse order? Diego Woitasen
2012-03-13 2:32 ` Stephen Hemminger
2012-03-13 6:15 ` Bill Fink
2012-03-13 6:52 ` David Miller
2012-03-13 14:26 ` Diego Woitasen
2012-03-13 16:47 ` Eric Dumazet
2012-03-13 15:37 ` Ben Greear [this message]
2012-03-14 5:30 ` Bill Fink
2012-03-14 5:32 ` Stephen Hemminger
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=4F5F69C6.7000900@candelatech.com \
--to=greearb@candelatech.com \
--cc=billfink@mindspring.com \
--cc=davem@davemloft.net \
--cc=diego@woitasen.com.ar \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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;
as well as URLs for NNTP newsgroup(s).