All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: nl80211 userspace
Date: Thu, 15 Feb 2007 09:19:44 -0500	[thread overview]
Message-ID: <20070215141944.GA3310@tuxdriver.com> (raw)
In-Reply-To: <40f31dec0702150017x3ecfca57ucded8f1d88bbb121@mail.gmail.com>

On Thu, Feb 15, 2007 at 10:17:50AM +0200, Nick Kossifidis wrote:
> I think it would be nice to have ifconfig for all interface
> configuration as they have done in openbsd, it's better to have one
> tool for all. What do you think ?

I think I'd lean to a separate tool, analagous to ethtool.

Anyway, the problem with using ifconfig is that it is generally
considered to be deprecated in favor of 'ip' (i.e. the iproute2
utility).  So increasing dependence on ifconfig would seem to be a
bad idea.

John

P.S.  Michael is, of course, right that the tool for users probably
should not rely on python (or perl, et al).  FWIW, I got the
impression that Johannes's tool was meant to use in the short-run
for developers...?
-- 
John W. Linville
linville@tuxdriver.com

  parent reply	other threads:[~2007-02-15 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 19:04 nl80211 userspace Johannes Berg
2007-02-15  8:17 ` Nick Kossifidis
2007-02-15  9:54   ` Michael Buesch
2007-02-15 14:19   ` John W. Linville [this message]
2007-02-15 15:05     ` Johannes Berg
2007-02-15 19:46       ` Luis R. Rodriguez
2007-02-15 19:48         ` Luis R. Rodriguez
2007-02-15 15:04   ` Johannes Berg

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=20070215141944.GA3310@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mickflemm@gmail.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.