linux-kernel - Re: GPLv3 Position Statement

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: <20060929124707.GB4931@ucw.cz>
Date:	Fri, 29 Sep 2006 12:47:07 +0000
From:	Pavel Machek <pavel@....cz>
To:	Theodore Tso <tytso@....edu>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Sergey Panov <sipan@...an.org>,
	James Bottomley <James.Bottomley@...elEye.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: GPLv3 Position Statement

Hi!

> And given that Stallman has announced that the new LGPL will be (to
> use programming terms) a subclass of GPLv3, it means that the LGPLv3
> is by extension incompatible with the GPLv2.  So that means that there
> will have to be two different versions of glibc (and every other
> shared library) shipped with every distributions --- one which is
> GPLv2, and one which is GPLv3.  And this fork is going to be forced by
> the FSF!  

Whats the problem? FSF does not do any programming itself. It will
force a fork, but world will just ignore the fork for glibc.

-- 
Thanks for all the (sleeping) penguins.
-
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/