From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: pmarques@grupopie.com, greg@kroah.com, nemosoft@smcc.demon.nl,
linux-usb-devel@lists.sourceforge.net,
Linus Torvalds <torvalds@osdl.org>
Subject: pwc+pwcx is not illegal
Date: 27 Aug 2004 15:18:04 -0400 [thread overview]
Message-ID: <1093634283.431.6370.camel@cube> (raw)
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.
What protectable elements of the kernel have been
included within the driver? I don't see any.
Like we say to SCO, where are the lines of code?
Remember, nobody is distributing a kernel with
this driver linked in. Merely loading the driver
is obviously fair use of the kernel.
(BTW, something which is required for operation
is not protectable. See the Sega v. Accolade case.
Thus, mere usage of header files won't do. You
couldn't even use the C header files on any UNIX
system if that were the case. Let's not be silly.)
Is it "non-literal copying" that concerns you?
Heh. OK. Name the jurisdiction you like, and
describe the copyright infringement test accepted
by the courts in that jurisdiction.
For example, the US 10th Circuit uses the "abstraction,
filtration, comparison" test. The US 9th Circuit uses
the "Analytic Dissection" test. There are others.
I don't know of any such test under which the
closed-source part of the driver could be considered
to be a derived work of the Linux kernel. I can hardly
imagine one that would make the driver derived without
also making Linux derived from UNIX!
So anyway... where are the lines of code?
next reply other threads:[~2004-08-27 19:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 19:18 Albert Cahalan [this message]
2004-08-27 19:29 ` pwc+pwcx is not illegal 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
-- 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=1093634283.431.6370.camel@cube \
--to=albert@users.sf.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=nemosoft@smcc.demon.nl \
--cc=pmarques@grupopie.com \
--cc=torvalds@osdl.org \
/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