[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ork5u3mjkf.fsf@oliva.athome.lsd.ic.unicamp.br>
Date: Sat, 16 Jun 2007 22:54:56 -0300
From: Alexandre Oliva <aoliva@...hat.com>
To: Bron Gondwana <brong@...tmail.fm>
Cc: Ingo Molnar <mingo@...e.hu>, Alan Cox <alan@...rguk.ukuu.org.uk>,
Daniel Hazelton <dhazelton@...er.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg KH <greg@...ah.com>,
debian developer <debiandev@...il.com>, david@...g.hm,
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 Jun 16, 2007, Bron Gondwana <brong@...tmail.fm> wrote:
> I obviously wasn't clear enough. The only way to come into complience
> with GPL3dd4 is to reduce your ability to fix things or grant everyone
> else the ability to mess with things. This severely restricts you from
> doing _anything_ in certain problem spaces due to local laws on the
> topic, even if you're an otherwise good actor who is making worthwhile
> source code contributions to the rest of the community.
I don't know any law that requires tivoization.
There may be laws that require certification or limitations on the
user. Manufacturer giving up the ability to make modifications would
address this, or *perhaps* arranging for user and manufacturer to each
hold half of the key needed to run a modification (which might comply
with the GPLv3dd4 terms, IANAL).
There may be business models that require the ability to make changes.
Then it's fair to enable the user to make changes as well, such that
they don't become dependent on the vendor, or even have their
1st-generation TiVo boxes left out in the cold for a while when the US
changes the DST rules again ;-)
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist oliva@...d.ic.unicamp.br, gnu.org}
-
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