linux-kernel - Re: [PATCH] ath9k: make driver usable standalone

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1313695090.23920.2.camel@dcbw.foobar.com>
Date:	Thu, 18 Aug 2011 14:18:09 -0500
From:	Dan Williams <dcbw@...hat.com>
To:	Valdis.Kletnieks@...edu
Cc:	Gábor Stefanik <netrolller.3d@...il.com>,
	Pavel Ivanov <paivanof@...il.com>,
	"Luis R. Rodriguez" <lrodriguez@...eros.com>,
	Jouni Malinen <jmalinen@...eros.com>,
	Vasanthakumar Thiagarajan <vasanth@...eros.com>,
	Senthil Balasubramanian <senthilkumar@...eros.com>,
	linux-wireless@...r.kernel.org, ath9k-devel@...ema.h4ckr.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ath9k: make driver usable standalone

On Wed, 2011-08-17 at 18:51 -0400, Valdis.Kletnieks@...edu wrote:
> On Wed, 17 Aug 2011 18:25:49 +0200, Gábor Stefanik said:
> 
> > Iwconfig and iwlist are themselves deprecated. Iw is the new wireless
> > configuration tool.
> 
> Somebody better tell Fedora Rawhide - as of the version released on July 27,
> their 'initscripts' RPM was still using iwconfig in /etc/sysconfig/network-scripts/ifup-wireless
> 
> So don't be quite so fast to be declaring WIRELESS_EXT dead just yet.

Given that nobody has stepped up to write patches to convert them to use
iw (or wpa_supplicant in the *correct* manner), and that for the most
part wifi on Fedora goes through NetworkManager and/or wpa_supplicant,
it's not surprising.  I don't have any particular interest in keeping
the existing ifup-wireless iwconfig hackery around, instead if it's
converted at all, it should be converted to use wpa_supplicant instead,
in the manner in which I've described in the various bug reports that
keep coming up.  That means not just pointing wpa_supplicant at a config
file, but instead keeping the options in the ifcfg file and writing out
a temporary wpa_supplicant config on-the-fly so that it integrates with
existing administrator expectations and workflow.

Dan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/