linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Cc: Theodore Tso <tytso@mit.edu>, Al Viro <viro@ftp.linux.org.uk>,
	davids@webmaster.com,
	"Linux-Kernel\@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?
Date: Mon, 25 Jun 2007 16:54:52 -0300	[thread overview]
Message-ID: <orhcov7qsz.fsf@oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20070625132853.GH10008@csclub.uwaterloo.ca> (Lennart Sorensen's message of "Mon\, 25 Jun 2007 09\:28\:53 -0400")

On Jun 25, 2007, lsorense@csclub.uwaterloo.ca (Lennart Sorensen) wrote:

> On Fri, Jun 22, 2007 at 03:00:30AM -0300, Alexandre Oliva wrote:
>> I was here to dispell the lies that were being spread about GPLv3, the
>> spirit and the goals of the GPL, as far as I understood them.

> Just because someone has a different opinion than you or the FSF does
> not make what they say a lie.

As a general statement, yours is absolutely correct.

However, the situation at hand is quite different AFAICT.  It's about
people repeatedly making statements that misconstrued the intent of a
third party, even after having been drawn attention to this.  AFAICT,
both elements needed to characterize lying are present: deviation from
the truth, and intent to instill the incorrect statements on others as
if they were true.

Now, it might be that those making such statements hadn't fully
realized what they were writing on was on others' intentions, rather
than objective facts or their own opinions, and that they didn't
realize they were misrepresenting those intentions before I brought
this up here.  In this case, if they confirm it, I'll be delighted to
retract my assessment of such behavior as 'lying'.

> Well what the spirit is, is certainly debateable,

If you misunderstand what 'the spirit of a legal text' as something
other than the intent of whoever wrote that document, then yes, it is
debatable.  You may want to take up the alleged inaccuracy to
Wikipedia: http://en.wikipedia.org/wiki/Letter_and_spirit_of_the_law

  When one obeys the letter of the law but not the spirit, he is
  obeying the literal interpretation of the words (the "letter") of
  the law, but not the intent of those who wrote the law. Conversely,
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  when one obeys the spirit of the law but not the letter, he is doing
  what the authors of the law intended, though not adhering to the
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  literal wording.

> Any organization that claims anyone that doesn't agree with its view of
> thw world and its interpretation of some written text is "confused" will
> be treated like all other religigous fanatics, and not listened too.

I suppose it thus follows that people will then take this perception
further and selectively ignore portions of texts written by these
parties.  And then become frustrated and complain when their
conclusions don't match those that are evidently encoded in the
portions that were ignored by them.  And then complain when they're
misunderstanding the text, or when they're characterized as confused,
or however else their selective attention and its misleading
consequences are characterized.

> Intelligent people know better than to listen to such groups.

Ignoring facts that don't fit your ideology, or that support an
ideology you reject, will mislead you, no matter what your fanaticism
or anti-fanaticism is.

> I think I know exactly as much about the GPL now as I did two weeks ago.

Good for you (assuming you're not saying you've refused to learn
anything just because I was the one passing on the knowledge, because,
well, this would be unintelligent too, right? ;-)


Consider this scenario: vendor tivoizes Linux in the device, and
includes the corresponding sources only in a partition that is
theoretically accessible using the shipped kernel, but that nothing in
the software available in the machine will let you get to.  Further,
sources (like everything else on disk) are encrypted, and you can only
decrypt it with hardware crypto that is disabled if the boot loader
doesn't find a correct signature for the boot partition, or maybe the
signature is irrelevant, given that everything on disk is encrypted in
such a way that, if you don't have the keys, you can't update the
kernel properly anyway.  The vendor refuses to give customers other
copies of the sources.  To add insult to the injury, the vendor
configures the computer to set up the encrypted disk partition
containing the sources as a swap device, such that the shared-secret
key used to access that entire filesystem is overwritten upon the
first boot, rendering the entire previous contents of the partition
holding the source code into an incomprehensible stream of bits.

Does anyone think this is permitted by the letter of GPLv2?  Is it in
the spirit of GPLv2?  How are the sources passed on in this way going
to benefit the user or the community?

Is this still desirable by the Linux developers?

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

  reply	other threads:[~2007-06-25 20:28 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21  9:39 how about mutual compatibility between Linux's GPLv2 and GPLv3? Alexandre Oliva
2007-06-21 11:35 ` jimmy bahuleyan
2007-06-21 17:53   ` Alexandre Oliva
2007-06-21 18:00     ` david
2007-06-21 20:02       ` Alexandre Oliva
2007-06-21 21:13         ` David Schwartz
2007-06-21 23:37           ` Alexandre Oliva
2007-06-22  0:31             ` David Schwartz
2007-06-22  1:00               ` Alexandre Oliva
2007-06-22  1:34                 ` Al Viro
2007-06-22  4:19                   ` Theodore Tso
2007-06-22  6:00                     ` Alexandre Oliva
2007-06-22 14:43                       ` Theodore Tso
2007-06-25 13:28                       ` Lennart Sorensen
2007-06-25 19:54                         ` Alexandre Oliva [this message]
2007-06-26  4:10                           ` Jan Harkes
2007-06-26  6:33                             ` Alexandre Oliva
2007-06-26  7:47                               ` Alexandre Oliva
2007-06-26 16:25                                 ` Jan Harkes
2007-06-27 23:08                                   ` Alexandre Oliva
2007-06-27 23:53                                     ` David Schwartz
2007-06-28  0:56                                       ` Alexandre Oliva
2007-06-28  1:37                                         ` David Schwartz
2007-06-28  2:37                                           ` Alexandre Oliva
2007-06-28  2:51                                             ` Daniel Hazelton
2007-06-28  4:45                                               ` Alexandre Oliva
2007-06-28  4:52                                                 ` Daniel Hazelton
2007-06-28  6:15                                                 ` David Schwartz
2007-06-28 17:40                                                   ` Alexandre Oliva
2007-06-28 19:13                                                     ` David Schwartz
2007-06-30  2:53                                                       ` Alexandre Oliva
2007-06-30  4:04                                                         ` David Schwartz
2007-06-30  6:16                                                           ` Alexandre Oliva
2007-06-28  3:44                                         ` David Schwartz
2007-06-28  4:57                                           ` Alexandre Oliva
2007-06-28  5:08                                     ` Jan Harkes
2007-06-28  6:58                                       ` Alexandre Oliva
2007-06-28 17:52                                         ` Alexandre Oliva
2007-07-01  8:48                                           ` Alexandre Oliva
2007-06-22  9:14                     ` Alan Cox
2007-06-22 14:47                       ` Theodore Tso
2007-06-22 19:14                         ` Alexandre Oliva
2007-06-22  4:26                   ` Alexandre Oliva
2007-06-22  5:23                     ` Al Viro
2007-06-22  6:15                       ` Alexandre Oliva
2007-06-22  9:05               ` Alan Cox
2007-06-22 21:28                 ` David Schwartz
2007-06-21 20:44     ` Jesper Juhl
2007-06-21 23:08       ` Alexandre Oliva
2007-06-21 23:20         ` Jesper Juhl
2007-06-22  0:13           ` Alexandre Oliva
2007-06-21 18:00 ` Al Viro
2007-06-21 20:15   ` Alexandre Oliva
2007-06-21 23:04     ` Al Viro
2007-06-22  0:47       ` Alexandre Oliva
2007-06-21 18:29 ` David Schwartz
2007-06-21 19:56   ` Alexandre Oliva
2007-06-21 20:48     ` David Schwartz
2007-06-21 23:23       ` Alexandre Oliva
2007-06-22  0:58         ` Jan Harkes
2007-06-22  4:14           ` Alexandre Oliva
2007-06-22  4:59             ` Jan Harkes
2007-06-22  1:33         ` Bron Gondwana
2007-06-22  4:40           ` Alexandre Oliva
2007-06-22  1:18 ` Bron Gondwana
2007-06-22  4:34   ` Alexandre Oliva
2007-06-22  5:25     ` Al Viro
2007-06-22  5:31     ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=orhcov7qsz.fsf@oliva.athome.lsd.ic.unicamp.br \
    --to=oliva@lsd.ic.unicamp.br \
    --cc=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=tytso@mit.edu \
    --cc=viro@ftp.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).