From: Jiri Benc <jbenc@suse.cz>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Michael Wu <flamingice@sourmilk.net>,
netdev@vger.kernel.org, Olivier <o.cornu@gmail.com>
Subject: Re: Dscape ieee80211: enabling/disabling the radio
Date: Wed, 10 May 2006 15:55:59 +0200 [thread overview]
Message-ID: <20060510155559.6875b58d@griffin.suse.cz> (raw)
In-Reply-To: <200605101537.15213.IvDoorn@gmail.com>
On Wed, 10 May 2006 15:37:11 +0200, Ivo van Doorn wrote:
> True, I agree here. But when rt2x00 was using the ipw stack a much
> requested feature from users was to be able to perform scanning while
> interface was down. (The requests did not specify if it they wanted passive or active scanning)
> But the reason for these requests was that some user space applications and/or
> distribution network scripts relied on the fact that the driver was capable of scanning
> while the interface was down, so the interface would only be brought up at boot time,
> when there was no desired AP in the scan result.
Such applications and scripts are broken. Let your users fill bug
reports to their distribution bugzillas.
> I don't know which distributions or user space application these were, but due to the amount
> of these requests it had been considered an important feature.
I wouldn't consider breaking the way the whole Linux networking works as
a feature.
Jiri
--
Jiri Benc
SUSE Labs
next prev parent reply other threads:[~2006-05-10 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 12:00 Dscape ieee80211: enabling/disabling the radio Ivo van Doorn
2006-05-09 22:01 ` Ivo van Doorn
2006-05-09 22:36 ` Michael Wu
2006-05-10 5:29 ` Olivier
2006-05-10 13:37 ` Ivo van Doorn
2006-05-10 13:55 ` Jiri Benc [this message]
2006-05-10 10:52 ` Jiri Benc
2006-05-10 13:55 ` Ivo van Doorn
2006-05-10 10:42 ` Jiri Benc
2006-05-10 13:53 ` Ivo van Doorn
2006-05-10 14:10 ` Jiri Benc
2006-05-10 17:03 ` Jouni Malinen
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=20060510155559.6875b58d@griffin.suse.cz \
--to=jbenc@suse.cz \
--cc=flamingice@sourmilk.net \
--cc=ivdoorn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=o.cornu@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 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).