From: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches
Date: Wed, 31 Aug 2005 11:27:41 -0600 [thread overview]
Message-ID: <4315E88D.9020603@soleranetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0508311432270.16968@cuia.boston.redhat.com>
Rik van Riel wrote:
>On Wed, 31 Aug 2005, Jeff V. Merkey wrote:
>
>
>
>>The Core File System code is a separate proprietary module and is not
>>released under the GPL
>>
>>
>
>Are you going to post an analysis on the legality of this
>on merkeylaw.com ? ;)
>
>
>
I am very open to discussions of this. Please go ahead and argue the
merits of GPL vs. proprietary code. DSFS is platform
neutral and will also run on Windows XP/2000/2003/Longhorn and Free BSD.
It uses no kernel headers or kernel
files.
I have always taken the position that the GPL does not convert IP
ownership. Since DSFS is hardware specific to
our platforms, I do not believe it entails any issues with the GPL, and
it uses published exports from the Linux kernel.
The GPL also confers right to copy == copyright under US copyright laws.
I don't believe that app vendors infringe
the GPL on Linux. This is just another app, and I have disclosed and
published all GPL code affected.
The GPL terms that require GPL conversion of any code that runs on Linux
is not supported by US Law. Many would
disagree, but that's OK. In short, it's just like any other proprietary
app running on Linux. If it uses no Linux code (which
it does not), then the GPL does not apply to it .
Jeff
next prev parent reply other threads:[~2005-08-31 18:42 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 [this message]
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
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=4315E88D.9020603@soleranetworks.com \
--to=jmerkey@soleranetworks.com \
--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