From: Albert Cahalan <albert@users.sf.net>
To: Paulo Marques <pmarques@grupopie.com>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
nemosoft@smcc.demon.nl, linux-usb-devel@lists.sourceforge.net
Subject: Re: pwc+pwcx is not illegal
Date: 27 Aug 2004 17:34:36 -0400 [thread overview]
Message-ID: <1093642476.431.6540.camel@cube> (raw)
In-Reply-To: <412F8CDD.7030107@grupopie.com>
On Fri, 2004-08-27 at 15:34, Paulo Marques wrote:
> Albert Cahalan wrote:
> > Paulo Marques writes:
> >>About the legal aspects of all this, they have been
> >>discussed extensively in the past. It is not about
> >>"hey this is just a simple hook", it is all about
> >>the derived work concept. This driver does absolutely
> >>nothing outside the kernel. It's only purpose is to
> >>attach itself to the kernel and to provide the images
> >>from the camera to userspace using the kernel ABI's.
> >>So you can not say it is not a derived work at all.
> >
> >
> > (note: the following is not legal advice)
> >
> > I think you'll find that this is not supported by
> > the copyright law, at least in the United States and
> > in any sane country.
> >
> > Richard Stallman and The SCO Group might like your
> > interpretation, at least when it serves them, but
> > that doesn't make it the law.
>
> You're completely missing the point. I never said that the pwcx driver
> copies code from the kernel, and in doing so infringes copyright law.
>
> What I'm saying is that the kernel is distributed with a license that
> allows you certain rights, and that extending the kernel functionality
> through closed source drivers is not one of those rights.
True, but misleading.
The GPL is not an EULA contract that makes you give
up your right to extend kernel functionality.
The GPL doesn't grant you the right to read the code,
but nobody complains that code reading is prohibited.
Such activities are outside the scope of the GPL.
> It is a derived work, not a "copied" work. The point is:
>
> >>This driver does absolutely
> >>nothing outside the kernel. It's only purpose is to
> >>attach itself to the kernel and to provide the images
> >>from the camera to userspace using the kernel ABI's.
Whatever. I don't see how that matters.
To be a derived work, some protectable element of
the kernel would have to be included. That might be
limited to lines of code, or it might include some
higher-level features like control flow. Either way,
the pwcx driver won't qualify as being derived.
The SCO Group has a better chance than you do. :-)
(and, if you're right, BAD things happen)
next prev parent reply other threads:[~2004-08-27 21:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 19:18 pwc+pwcx is not illegal Albert Cahalan
2004-08-27 19:29 ` Linus Torvalds
2004-08-27 20:06 ` Kenneth Lavrsen
2004-08-27 20:21 ` Linus Torvalds
2004-08-27 20:24 ` David S. Miller
2004-08-27 20:26 ` Paul Jakma
2004-08-30 17:41 ` Brian Litzinger
2004-08-27 20:38 ` David Ford
2004-08-27 20:57 ` Albert Cahalan
2004-08-27 21:04 ` Greg KH
2004-08-27 21:09 ` Linus Torvalds
2004-08-29 14:00 ` Alan Cox
2004-08-29 16:33 ` Nemosoft Unv.
2004-08-29 15:42 ` Alan Cox
2004-08-29 17:17 ` [linux-usb-devel] " Randy.Dunlap
2004-08-29 17:16 ` Norbert van Nobelen
2004-08-27 19:34 ` Paulo Marques
2004-08-27 21:34 ` Albert Cahalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-28 8:15 Gabucino
2004-08-28 10:30 ` Vojtech Pavlik
2004-08-28 12:18 Kenneth Lavrsen
2004-08-28 13:11 ` Adrian Bunk
2004-08-28 15:24 ` Kenneth Lavrsen
2004-08-29 14:02 ` Alan Cox
2004-09-01 22:51 ` Rogier Wolff
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=1093642476.431.6540.camel@cube \
--to=albert@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=nemosoft@smcc.demon.nl \
--cc=pmarques@grupopie.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