From: Steven Rostedt <rostedt@goodmis.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: legal@lists.gnumonks.org, linux-fsdevel@vger.kernel.org,
LKML Kernel <linux-kernel@vger.kernel.org>,
"Robert W. Fuller" <garbageout@sbcglobal.net>
Subject: Re: blatant GPL violation of ext2 and reiserfs filesystem drivers
Date: Thu, 22 Dec 2005 15:27:21 -0500 [thread overview]
Message-ID: <1135283241.12761.19.camel@localhost.localdomain> (raw)
In-Reply-To: <496FC071-3999-4E23-B1A2-1503DCAB65C0@mac.com>
On Thu, 2005-12-22 at 13:01 -0500, Kyle Moffett wrote:
> On Dec 22, 2005, at 11:08, Robert W. Fuller wrote:
> > Please see the following thread:
> >
> > http://www.opensolaris.org/jive/thread.jspa?threadID=2132&tstart=0x
> >
> > Sorry I didn't get around to reporting this sooner, but at least
> > the guilty party has had plenty of time to fail to repent.
> >
> > Regards,
> >
> > Rob
>
> This case looks about as black and white as it gets (although IANAL),
> so I'm adding gpl-violations.org-legal to the CC list.
I'm not sure this is the case here or not, but it definitely brings up
an interesting question.
Since the dynamic loading of binary modules into Linux seems to be a
gray area, since if I give you a binary module that loads into Linux,
but except for the API found in the header files, the module contains no
GPL code. Is it bound to the GPL? This is a rhetorical question, please
don't answer it.
Now the real question: If one were to have an operating system, and set
up a layer that simulated the API of Linux, such that Linux binary
modules could be loaded, is _that_ a violation of the GPL? IOW, one
would only distribute to you a system that has no GPL code, and only
simulates an API, which is legal otherwise Samba wouldn't exist. But the
user has the option of compiling a Linux module to get the benefits from
it. Sort of a ndiswrapper in reverse!
-- Steve
next prev parent reply other threads:[~2005-12-22 20:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 16:08 blatant GPL violation of ext2 and reiserfs filesystem drivers Robert W. Fuller
2005-12-22 18:01 ` Kyle Moffett
2005-12-22 20:27 ` Steven Rostedt [this message]
2005-12-22 21:46 ` Bryan Henderson
2005-12-22 23:12 ` Jeff V. Merkey
2005-12-23 2:56 ` Chris Wedgwood
2005-12-23 3:15 ` Diego Calleja
2005-12-23 3:28 ` Chris Wedgwood
2005-12-23 3:38 ` Steven Rostedt
2005-12-23 3:49 ` Matthew Wilcox
2005-12-23 4:25 ` Jamie Lokier
2005-12-23 3:30 ` Adrian Bunk
2005-12-23 15:35 ` Ben Slusky
2005-12-23 19:34 ` Bryan Henderson
2005-12-23 20:16 ` Scott Mansfield
2005-12-23 22:00 ` Bryan Henderson
2005-12-24 1:48 ` Horst von Brand
2005-12-24 2:41 ` Peter Williams
2005-12-24 3:25 ` Jamie Lokier
2006-01-04 11:09 ` Harald Welte
2006-01-04 11:54 ` Jamie Lokier
2006-01-04 13:18 ` Harald Welte
2006-01-04 13:46 ` Matthew Wilcox
2006-01-04 17:46 ` Harald Welte
2006-01-04 14:16 ` Jamie Lokier
2006-01-04 14:45 ` Matthew Wilcox
2006-01-04 15:57 ` Jamie Lokier
2006-01-04 17:42 ` Harald Welte
2006-01-05 17:52 ` Bryan Henderson
2006-01-05 17:30 ` Bryan Henderson
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=1135283241.12761.19.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=garbageout@sbcglobal.net \
--cc=legal@lists.gnumonks.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.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