From: jamal <hadi@cyberus.ca>
To: Patrick McHardy <kaber@trash.net>
Cc: Stephen Hemminger <shemminger@vyatta.com>, netdev@vger.kernel.org
Subject: Re: PATCH WAS( Re: [ANNOUNCE] iproute2 v2.6.25
Date: Sun, 20 Apr 2008 07:48:48 -0400 [thread overview]
Message-ID: <1208692128.12249.26.camel@localhost> (raw)
In-Reply-To: <480A21AF.1040405@trash.net>
On Sat, 2008-19-04 at 18:45 +0200, Patrick McHardy wrote:
> I imagine something like this:
>
> # nl-link-dump env eth0
>
> LINK_NAME=eth0
> LINK_IFINDEX=2
> LINK_LLADDR=.....
> LINK_OPERSTATE=...
>
> and so on. You could then do something like this:
>
> export $(nl-link-dump env eth0)
>
> and use $LINK_... in your scripts.
>
Clever. That would certainly help in portability; i will take a closer
look on what you did for libnl and see how well it applies for iproute2.
Stephen, I have some cycles today - I am going to assume no-response
from you implies ok on the change i sent earlier - so i will work on
adding additional changes on top of the one i sent earlier to fixup the
pretty printing (which is not as serious a regression IMO as breakage of
the output).
cheers,
jamal
next prev parent reply other threads:[~2008-04-20 11:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 17:38 [ANNOUNCE] iproute2 v2.6.25 Stephen Hemminger
2008-04-17 20:35 ` PATCH WAS( " jamal
2008-04-17 20:46 ` Stephen Hemminger
2008-04-17 20:59 ` jamal
2008-04-17 21:08 ` Stephen Hemminger
2008-04-17 21:24 ` jamal
2008-04-18 12:45 ` jamal
2008-04-18 14:22 ` Patrick McHardy
2008-04-19 0:08 ` jamal
2008-04-19 0:59 ` Stephen Hemminger
2008-04-19 1:34 ` jamal
2008-04-19 16:45 ` Patrick McHardy
2008-04-20 11:48 ` jamal [this message]
2008-04-21 11:50 ` Patrick McHardy
2008-04-21 13:07 ` jamal
2008-04-21 13:39 ` Patrick McHardy
2008-04-21 14:21 ` jamal
2008-04-28 11:52 ` Thomas Graf
2008-04-28 11:44 ` Thomas Graf
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=1208692128.12249.26.camel@localhost \
--to=hadi@cyberus.ca \
--cc=kaber@trash.net \
--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).