All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Oeser <netdev@axxeo.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: dlang@digitalinsight.com, kaber@trash.net, marcel@holtmann.org,
	mbuesch@freenet.de, jgarzik@pobox.com,
	bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Bcm43xx-dev] [Fwd: State of the Union: Wireless]
Date: Mon, 9 Jan 2006 19:24:26 +0100	[thread overview]
Message-ID: <200601091924.26575.netdev@axxeo.de> (raw)
In-Reply-To: <20060106.141836.41371212.davem@davemloft.net>

David S. Miller wrote:
> From: David Lang <dlang@digitalinsight.com>
> Date: Fri, 6 Jan 2006 14:16:17 -0800 (PST)
> 
> > character devices are far easier to script. this really sounds like the 
> > type of configuration stuff that sysfs was designed for. can we avoid yet 
> > another configuration tool that's required?
> 
> netlink is being recommended exactly because it can result
> in only needing one tool for everything

Yes, iproute2 rocks!

I recently discovered that it can do "xfrm" stuff and was amazed to
see that the developer(s) had a big clue about what we like to
see (and what is human readable), if we type "ip xfrm state" 
and "ip xfrm policy" as opposed to "setkey -D" and "setkey -PD".

So I can only hope that netlink and iproute will be chosen as a way
to represent it to the user, just because of the clueful developers of
iproute2.


Regards

Ingo Oeser


  reply	other threads:[~2006-01-09 18:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1136541243.4037.18.camel@localhost>
2006-01-06 11:00 ` [Bcm43xx-dev] [Fwd: State of the Union: Wireless] Michael Buesch
2006-01-06 11:38   ` Marcel Holtmann
2006-01-06 11:45     ` Michael Buesch
2006-01-06 11:45       ` Michael Buesch
2006-01-06 12:10       ` [Bcm43xx-dev] " Marcel Holtmann
2006-01-06 12:46         ` Patrick McHardy
2006-01-06 18:23           ` Stephen Hemminger
2006-01-06 22:16           ` David Lang
2006-01-06 22:18             ` David S. Miller
2006-01-09 18:24               ` Ingo Oeser [this message]
2006-01-06 22:22             ` Patrick McHardy
2006-01-12 14:20           ` Harald Welte
2006-01-06 16:12       ` Feyd
2006-01-06 16:25         ` Johannes Berg
2006-01-06 16:04   ` State of the Union: Wireless Mike Kershaw
2006-01-06 17:02   ` [Bcm43xx-dev] [Fwd: State of the Union: Wireless] Ben Greear
     [not found] <5rXDU-5s4-7@gated-at.bofh.it>
     [not found] ` <5rXDU-5s4-5@gated-at.bofh.it>
2006-01-06 22:57   ` Bodo Eggert
2006-01-06 22:57     ` Bodo Eggert

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=200601091924.26575.netdev@axxeo.de \
    --to=netdev@axxeo.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=davem@davemloft.net \
    --cc=dlang@digitalinsight.com \
    --cc=jgarzik@pobox.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mbuesch@freenet.de \
    --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 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.