From: Stephen Hemminger <shemminger@vyatta.com>
To: hadi@cyberus.ca
Cc: Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org
Subject: Re: PATCH WAS( Re: [ANNOUNCE] iproute2 v2.6.25
Date: Fri, 18 Apr 2008 17:59:41 -0700 [thread overview]
Message-ID: <20080418175941.2ae6506f@extreme> (raw)
In-Reply-To: <1208563696.4450.43.camel@localhost>
On Fri, 18 Apr 2008 20:08:16 -0400
jamal <hadi@cyberus.ca> 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?
>
> cheers,
> jamal
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
If somebody doesn't do it first, maybe split the u32 output into:
(nothing) original format
-raw value/offset
-pretty decoded equivalent of original command
next prev parent reply other threads:[~2008-04-19 0:59 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 [this message]
2008-04-19 1:34 ` jamal
2008-04-19 16:45 ` Patrick McHardy
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=20080418175941.2ae6506f@extreme \
--to=shemminger@vyatta.com \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.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 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).