From: Martijn van Oosterhout <kleptog@svana.org>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Giacomo Catenazzi <cate@debian.org>,
Michael Elizabeth Chastain <mec@shout.net>,
jgarzik@mandrakesoft.com, kbuild-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] Re: Disgusted with kbuild developers
Date: Tue, 19 Feb 2002 21:16:11 +1100 [thread overview]
Message-ID: <20020219211611.B27403@svana.org> (raw)
In-Reply-To: <fa.i8v9q2v.6g8h03@ifi.uio.no> <fa.hhvfopv.1f70hqv@ifi.uio.no> <3C7206FD.2050306@debian.org> <E16d6Mn-00011Q-00@starship.berlin>
In-Reply-To: <E16d6Mn-00011Q-00@starship.berlin>; from phillips@bonn-fries.net on Tue, Feb 19, 2002 at 10:15:16AM +0100
On Tue, Feb 19, 2002 at 10:15:16AM +0100, Daniel Phillips wrote:
> Under the GPL Having exclusive copyright just means that you can relicense
> later stuff if you want. I'm not clear on why FSF considers it so important
> but for Linux it just means that nobody, not even Linus, can ever release
> under a new license (e.g., the BSD license). So actually, having multiple
> copyright holders is a good thing for you, it protects your investment in GPL
> capital better. I say, if Microsoft employees want to contribute to Linux,
> the more the merrier. Heck, even billg is going to wake up on day (with a
> start, in the middle of the night) and realize which way the wind is blowing.
> Steve Jobs did.
OTOH, having exclusive copyright means you can more successfully defend that
copyright. If someone took a copy of the linux kernel and used it in a
blatently non-GPL compliant way, who could sue?
>From the FSF website: If there are multiple authors of a copyrighted work,
successful enforcement depends on having the cooperation of all authors.
All the authors of the linux kernel? That would be more difficult than
herding Debian developers.
Since I don't think anyone has registered the copyright for the kernel
no-one would be eligable for statutory damages and actual damages is zero.
The Samba Team ran into exactly this problem. The Linux kernel lucky because
public opinion is in its favour.
Not that I think the FSF's way is necessarily the right way, but it is not
without merit.
--
Martijn van Oosterhout <kleptog@svana.org>
http://svana.org/kleptog/
> Terrorists can only take my life. Only my government can take my freedom.
next prev parent reply other threads:[~2002-02-19 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.i8v9q2v.6g8h03@ifi.uio.no>
[not found] ` <fa.hhvfopv.1f70hqv@ifi.uio.no>
2002-02-19 8:04 ` Disgusted with kbuild developers Giacomo Catenazzi
2002-02-19 8:13 ` Alexander Viro
2002-02-19 9:15 ` Daniel Phillips
2002-02-19 10:16 ` Martijn van Oosterhout [this message]
2002-02-19 10:39 ` [kbuild-devel] " Alan Cox
2002-02-19 21:06 ` Bill Davidsen
2002-02-20 11:43 ` Pavel Machek
2002-02-18 3:05 [kbuild-devel] " Michael Elizabeth Chastain
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=20020219211611.B27403@svana.org \
--to=kleptog@svana.org \
--cc=cate@debian.org \
--cc=jgarzik@mandrakesoft.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
--cc=phillips@bonn-fries.net \
/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