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: <Pine.LNX.4.64.0706191649490.26701@asgard.lang.hm>
Date:	Tue, 19 Jun 2007 16:57:04 -0700 (PDT)
From:	david@...g.hm
To:	Alexandre Oliva <aoliva@...hat.com>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Al Viro <viro@....linux.org.uk>,
	Bernd Schmidt <bernds_cb1@...nline.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Ingo Molnar <mingo@...e.hu>, Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Tue, 19 Jun 2007, Alexandre Oliva wrote:

> Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
> 
> On Jun 19, 2007, david@...g.hm wrote:
>
>> if a company doesn't care about tivoizing then they won't do it, it
>> takes time and money to tivoize some product and it will cause
>> headaches for the company.
>
>> their reasons for wanting to tivoize a product may be faulty, but they
>> think that the reasons are valid or they wouldn't go to the effort.
>
> Absolutely right.  And we'll get to that.  Please just be patient.
>
> In fact, how much the company cares about tivoizing is completely
> irrelevant to that point.  I shouldn't even have included it, but I
> did because I thought it would be useful as a boundary condition.
>
> So just disregard that.
>
> Is there agreement that, comparing tivoized and non-tivoized hardware,
> we get'd more contributions if the hardware is not tivoized, because
> users can scratch their own itches, than we would for tivoized
> hardware?

if you also make the assumption that the company won't use propriatary 
software instead then I think you would get agreement. but the 
disagrement is over this exact assumption. you assume that these companies 
will use non-tivoized products if you make it hard to use the software 
covered by the GPL, most other people are saying that they disagree and 
the result would be fewer companies useing software covered by GPL 
instead.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ