linux-kernel - Re: [madwifi-project] [RFC] Closing the project

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: <43e72e890811131254q35ff4f48xf58c7c26d5c9a5a4@mail.gmail.com>
Date:	Thu, 13 Nov 2008 12:54:07 -0800
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	"Pavel Roskin" <proski@....org>
Cc:	"Michael Renzmann" <mrenzmann@...wifi-project.org>,
	madwifi-project@...ts.madwifi-project.org,
	linux-wireless <linux-wireless@...r.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [madwifi-project] [RFC] Closing the project

On Thu, Nov 13, 2008 at 12:48 PM, Pavel Roskin <proski@....org> wrote:
> On Thu, 2008-11-13 at 11:42 -0800, Luis R. Rodriguez wrote:
>

>> > I think the biggest impediment to MadWifi development was not
>> > bureaucracy.  It was the non-free HAL.
>>
>> Not really, even with an alternative people are still used to coding
>> with it and find it easier to commit into an svn repository than
>> submit  patches upstream. Maybe our process is move involved but there
>> its also why Linux code has a certain quality in it. We tend to frown
>> upon crap. If MadWifi ever were to touch Linux it would be tainted
>> with CRAP.
>
> OK, HAL was not the only reason.  Let's say there is good bureaucracy
> and bad bureaucracy.  The difference is the former is helpful and the
> later is not.  The kernel is an excellent example of good bureaucracy
> that we should learn from.
>
> It would be great to have a detailed analysis why MadWifi failed.

It didn't fail, it was just not the best approach to support Linux
from the start, that's why *today* its just silly to go on with it,
specially since the vendor involved is *contributing* and helping to
implement support the right way.

>> Just my advice: let MadWifi die already, stop wasting your time.
>
> I understand what you mean, but I have to deal with MadWifi anyway.  As
> I said before, I'd rather share my fixes that keep them to myself.

Understood -- but perhaps you can identify what is lacking that you
need to better help push what is required and missing.

 Luis
--
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/