From: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
To: Valdis.Kletnieks@vt.edu
Cc: Arjan van de Ven <arjan@infradead.org>,
Rik van Riel <riel@redhat.com>,
linux <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches
Date: Wed, 31 Aug 2005 14:23:19 -0600 [thread overview]
Message-ID: <431611B7.6000103@soleranetworks.com> (raw)
In-Reply-To: <200508312128.j7VLST47010653@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>On Wed, 31 Aug 2005 12:00:45 MDT, "Jeff V. Merkey" said:
>
>
>
>> There's also a more fundamental problem with the GPL language. The GPL stated it
>>confers "RIGHT TO COPY". This is not the same as "RIGHT TO GRANT
>>LICENSES TO DISTRIBUTE." Under US copyright law, if you confer to any person
>>the "right to copy" in a license which states the software is FREE, you have in essense
>>affected a copyright transfer to each and every person who receives the
>>code.
>>
>>
>
>Bullshit.
>
>17 USC 106(3) talks about transfer of ownership *of the item*, not of the
>copyright itself (see 17 USC 202, which clarifies this). So you can sell a
>book - but that isn't transferring the copyright of the book. There isn't any
>actual transfer without a document that actually *SAYS* "transfer of copyright" -
>see 17 USC 204 (a) (Note that there's whole companies in Utah, with actual
>large legal teams, that seem unclear on the concept in 17 USC 204(a), so I'm
>not surprised that you're confused on this as well).
>
>
>
I have responded all I am going to on this topic. Further discussion
will not be helpful. The patches are provided
IAW the GPL. Our proprietary application is just like the thousands of
others provided on Linux, and it
does use or incorporate any GPL or Linux code.
I will not respond to any further discussion on this thread. Thanks for
the input. Please feel free to read Linus
statements on kernel.org regarding the statements that applications that
run on Linux and that use published
interfaces are unaffected by the GPL.
Thanks for your input.
Jeff
next prev parent reply other threads:[~2005-08-31 21:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 16:33 [ANNOUNCE] DSFS Network Forensic File System for Linux Patches Jeff V. Merkey
2005-08-31 18:32 ` Rik van Riel
2005-08-31 17:27 ` Jeff V. Merkey
2005-08-31 18:58 ` Arjan van de Ven
2005-08-31 18:00 ` Jeff V. Merkey
2005-08-31 21:28 ` Valdis.Kletnieks
2005-08-31 20:23 ` Jeff V. Merkey [this message]
2005-08-31 20:27 ` Jeff V. Merkey
2005-08-31 23:22 ` Diego Calleja
2005-08-31 22:50 ` jmerkey
2005-09-01 0:36 ` Bernd Eckenfels
2005-09-01 0:33 ` Bernd Eckenfels
2005-09-01 0:56 ` jmerkey
2005-09-01 1:44 ` jmerkey
[not found] ` <67029b1705083120142c0c1dea@mail.gmail.com>
2005-09-01 3:19 ` Zhou Yingchao
2005-09-01 7:12 ` Lincoln Dale
2005-09-01 7:45 ` Vojtech Pavlik
2005-09-01 10:23 ` Alan Cox
2005-09-01 8:28 ` Bernd Petrovitsch
2005-09-01 10:15 ` Alan Cox
2005-09-03 21:26 ` Bernd Eckenfels
2005-09-04 8:45 ` Alan Cox
2005-09-05 20:19 ` Bernd Eckenfels
2005-08-31 21:49 ` Jose Luis Domingo Lopez
2005-09-01 21:11 ` Alistair John Strachan
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=431611B7.6000103@soleranetworks.com \
--to=jmerkey@soleranetworks.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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