From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, paul@codesourcery.com
Subject: Re: [Qemu-devel] why is kqemu closed?
Date: Tue, 11 Apr 2006 09:43:01 -0600 (MDT) [thread overview]
Message-ID: <20060411.094301.57440985.imp@bsdimp.com> (raw)
In-Reply-To: <200604111636.25101.paul@codesourcery.com>
In message: <200604111636.25101.paul@codesourcery.com>
Paul Brook <paul@codesourcery.com> writes:
: > 4. There is a slippery slope here -
:
: There's a slippery slope both ways. If you assume vital parts of your system
: are going to be closed source then why bother with open source at all. Just
: use Windows or HPUX.
:
: > if Linux kernel policies can change
: > to force all kernel-space binding to be GPL (even though Linus decreed
: > that this is not the case years ago), what's next? Libraries that make
: > kernel interface calls should be GPL rather than LGPL?
:
: Now you're talking total nonsense.
:
: The GPL explicitly says that OS is exempt from the requirements placed on an
: application:
:
: "the source code distributed need not include
: anything that is normally distributed (in either source or binary
: form) with the major components (compiler, kernel, and so on) of the
: operating system on which the executable runs, unless that component
: itself accompanies the executable."
I think that you are missing the point. He's not saying that you have
to distribute the source (which is what that exemption is about).
He's saying that the license on a mere library cannot and should not
force applications linked with that library to become a derived work.
And he's right about that being a dangerous precident. If I call
write(2) in my application, the mere fact that the kernel is GPL'd
shouldn't matter for the license of my application. It is not a
derived work.
The circumlocutions that some people go through to try to show that
somehow using internal kernel interfaces make something a derived work
do border on the absurd and are a very agressive interpretation of
what makes a work a derived work. That interpretation needs to be
curbed, otherwise we'd have a slipperly slope where libc becomes GPL'd
and merely linking against it once and providing that binary infects
the application with the GPL (a position that no court has endorced).
Warner
next prev parent reply other threads:[~2006-04-11 15:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 15:16 [Qemu-devel] why is kqemu closed? Rakotomandimby Mihamina
2006-04-10 15:20 ` Hetz Ben Hamo
2006-04-10 15:47 ` Auke Kok
2006-04-10 15:55 ` Hetz Ben Hamo
2006-04-10 15:56 ` Leonardo E. Reiter
2006-04-11 4:37 ` Auke Kok
2006-04-11 7:58 ` Brad Campbell
2006-04-11 16:22 ` Jim C. Brown
2006-04-11 8:37 ` Ricardo Almeida
2006-04-11 9:46 ` Johannes Schindelin
2006-04-11 10:05 ` Jamie Lokier
2006-04-11 15:05 ` Leonardo E. Reiter
2006-04-11 15:14 ` Jonas Maebe
2006-04-11 15:25 ` Jim C. Brown
2006-04-11 16:04 ` Jonas Maebe
2006-04-11 15:36 ` Paul Brook
2006-04-11 15:43 ` M. Warner Losh [this message]
2006-04-11 16:00 ` Paul Brook
2006-04-11 16:29 ` M. Warner Losh
2006-04-11 16:09 ` Jim C. Brown
2006-04-11 17:10 ` Enough already! " Bakul Shah
2006-04-11 15:17 ` Sebastian Kaliszewski
2006-04-11 15:31 ` M. Warner Losh
2006-04-11 12:33 ` andrzej zaborowski
2006-04-11 13:58 ` Jamie Lokier
2006-04-11 15:10 ` Sebastian Kaliszewski
2006-04-11 15:19 ` M. Warner Losh
2006-04-10 15:57 ` Brett (Mare) Henley
2006-04-10 16:02 ` Leonardo E. Reiter
2006-04-10 19:11 ` M. Warner Losh
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=20060411.094301.57440985.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).