All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: Stephen Hemminger <shemminger@vyatta.com>, netdev@vger.kernel.org
Subject: Re: PATCH WAS( Re: [ANNOUNCE] iproute2 v2.6.25
Date: Sat, 19 Apr 2008 18:45:35 +0200	[thread overview]
Message-ID: <480A21AF.1040405@trash.net> (raw)
In-Reply-To: <1208563696.4450.43.camel@localhost>

jamal wrote:
> On Fri, 2008-18-04 at 16:22 +0200, Patrick McHardy wrote:
>
>   
>> Yes, that sucks (ran into the same problem with iproute in a
>> previous job). I added the ENV dump format to libnl a couple
>> of years ago (NAME=val), should be easy to add a set of simple
>> tools to get the information and export it in the environment.
>>     
>
> Can you explain this a little? Would these variables define what
> the command line parameters look like before invoking?

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.


  parent reply	other threads:[~2008-04-19 16:49 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 [this message]
2008-04-20 11:48                   ` jamal
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=480A21AF.1040405@trash.net \
    --to=kaber@trash.net \
    --cc=hadi@cyberus.ca \
    --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 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.