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:	Mon, 18 Jun 2007 08:45:49 -0700
From:	Greg KH <greg@...ah.com>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	Al Viro <viro@....linux.org.uk>,
	Daniel Hazelton <dhazelton@...er.net>,
	Bron Gondwana <brong@...tmail.fm>, Ingo Molnar <mingo@...e.hu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	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 Sun, Jun 17, 2007 at 02:56:24AM -0300, Alexandre Oliva wrote:
> 
> If you want your opinions to stand a chance to make a difference, the
> right place to provide them is gplv3.fsf.org/comments, and time is
> running short.

If you honestly think that the "anti-tivo" clause in GPLv3 will be
removed just because we start to add more comments to that page, then
you are sorely mistaken.  From the very _beginning_ of the v3 process
the kernel developers have showed their objection to that section of the
license, and we were told, to our face, with no uncertian terms, that it
was going to stay, in one form or another, no matter what we thought or
said about it.

So, why would we want to waste our time filling out web forms after
that?

greg k-h
-
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