mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Hards <bhards@bigpond.net.au>
To: Paul Menage <pmenage@ensim.com>
Cc: Paul Menage <pmenage@ensim.com>, linux-kernel@vger.kernel.org
Subject: Re: netlink documentation (was: of ethernet names)
Date: Tue, 11 Jun 2002 10:16:59 +1000	[thread overview]
Message-ID: <200206111016.59260.bhards@bigpond.net.au> (raw)
In-Reply-To: <E17HZBU-0000Jm-00@pmenage-dt.ensim.com>

On Tue, 11 Jun 2002 10:06, Paul Menage wrote:
> >But I can't even follow enough of iproute (or zebra, which also uses
> > netlink, AFAICT) to figure out how to do basic stuff like a list of
> > configured networking devices, or set the default route.
>
> E.g. to get the list of devices (untested, lacking error checking, etc),
> use something like:
Bingo! I think I see what is happening, just by inspection. Beverage of choice 
when we meet up!

Now, how did you get this? Just familarity with the API built up over time, 
pure zen, or copied from some other app?

A couple of days of playing with this, I might even be able to write the 
tutorial myself :)

Brad
-- 
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.

  reply	other threads:[~2002-06-11  0:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0C01A29FBAE24448A792F5C68F5EA47D29DD32@nasdaq.ms.ensim.com>
2002-06-10 23:20 ` of ethernet names (was [PATCH] Futex Asynchronous Paul Menage
2002-06-10 23:32   ` Brad Hards
2002-06-10 23:36     ` Randy.Dunlap
2002-06-11  0:11       ` Brad Hards
2002-06-11  0:06     ` netlink documentation (was: of ethernet names) Paul Menage
2002-06-11  0:16       ` Brad Hards [this message]
2002-06-11  0:40         ` Paul Menage
2002-06-11  2:25     ` of ethernet names (was [PATCH] Futex Asynchronous Andi Kleen
2002-06-11  2:34       ` Brad Hards

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=200206111016.59260.bhards@bigpond.net.au \
    --to=bhards@bigpond.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenage@ensim.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

all inboxes | Powered by JetHome®