linux-kernel - Re: [madwifi-project] Death to MadWifi!

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]

Date:	Tue, 12 May 2009 11:14:21 +0200
From:	Frans Pop <elendil@...net.nl>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	p0g0@...wifi-project.org, madwifi-project@...ema.h4ckr.net,
	Cliff.Holden@...eros.com, mb@...sch.de, nbd@...nwrt.org,
	mickflemm@...il.com, proski@....org, me@...copeland.com,
	juhosg@...nwrt.org, linux-kernel@...r.kernel.org
Subject: Re: [madwifi-project] Death to MadWifi!

Luis R. Rodriguez wrote:
> Trust me, I'm not concerned at all -- reason for me sending this
> e-mail was having to hear a rant from a user about MadWifi being such
> crap and about devices not being supported properly.

Let me give at least one counter example.

I have used madwifi in the past but switched to ath5k when it came 
available for my old Trust Atheros-based PCMCIA card, mostly because of 
the ease of compilation and partly because of the better "free-ness".

There is at least one area where the madwifi driver was and probably still 
is far superior: properly blinking the leds on the card to show the 
power/connection state and during data transfer.

It's not a major issue and though I've mentioned this at least once in a 
bug report or mail, this admittedly was back when there were more 
important things to fix. I probably should submit a proper bug report 
about it now.

I'm not asking for this to be fixed with this mail. I only mention it 
because the title and tone of this mail, and the fact of its recurring 
theme, offend me somewhat.
The way FOSS normally works is that one variant of alternative software 
will gradually die a natural death once a clear superior is established. 
There should be no need for members of rival projects to try to actively 
kill eachother off (the rival project that is, not its members).

Cheers,
FJP

P.S. This is the only post I've seen from this thread as apparently it 
started somewhere other than LKML.
--
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/