linux-kernel - Re: Wasting our Freedom

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: <46EDC3C4.2030602@pobox.com>
Date:	Sun, 16 Sep 2007 20:01:08 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	david@...g.hm
CC:	Jacob Meuser <jakemsr@....lonestar.org>,
	Theodore Tso <tytso@....edu>, Adrian Bunk <bunk@...nel.org>,
	"Can E. Acar" <can.acar@...-g.com.tr>, misc@...nbsd.org,
	linux-kernel@...r.kernel.org,
	Daniel Hazelton <dhazelton@...er.net>,
	Eben Moglen <moglen@...twarefreedom.org>,
	Lawrence Lessig <lessig_from_web@...ox.com>,
	"Bradley M. Kuhn" <bkuhn@...twarefreedom.org>,
	Matt Norwood <norwood@...twarefreedom.org>
Subject: Re: Wasting our Freedom

david@...g.hm wrote:
> you claim that it's unethical for the linux community to use the code, 
> but brag about NetApp useing the code. what makes NetApp ok and Linux 
> evil? many people honestly don't understand the logic behind this. 
> please explain it.

There are two highly relevant angles to this that nobody is mentioning:

1) Does it make sense to share code, at a technical level?

The fact is, BSD and Linux wireless stacks are quite different.  Linux 
also has a technical requirement that "Linux drivers look like Linux 
drivers."  This enables a vast array of source code checking tools like 
Coverity and sparse, as well as maximizing human reviewer bandwidth.

Therefore, there is a strong /technical/ motivation for the source code 
to diverge.  That's quite natural.

2) Information sharing is both rampant and healthy.

Linux and BSD projects share a vast amount of hardware knowledge, 
information on how to properly program hardware.  Linux folks use BSD 
code as /reference documentation/, and BSD folks do the same with Linux 
code.

This is far more efficient in many cases, due to the natural divergence 
of the respective codebases.  It is often easier to look at codebase A, 
and then mentally translate that into code for codebase B, than to 
directly copy and reuse code.

	Jeff

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