From: Pavel Machek <pavel@ucw.cz>
To: Jamie Lokier <jamie@shareable.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Using GPL'd Linux drivers with non-GPL, binary-only kernel
Date: Wed, 7 May 2003 17:18:11 +0200 [thread overview]
Message-ID: <20030507151811.GC412@elf.ucw.cz> (raw)
In-Reply-To: <20030507142619.GA16023@mail.jlokier.co.uk>
Hi!
> > > I'd get to define "the OS" so that is not a problem :) You could
> >
> > The GPL is smarter than that
> > "However, as a special exception, 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 am talking about replacing the kernel (and compiler as it
> happens)... those _are_ the major components of the operating system
> which fall under that exception. So, if we were splitting hairs over
> the wording, it would come down to whether the other major components
> "accompany the executable", where the executable is the GPL module.
>
> This is further complicated because those GPL modules need not be
> distributed in binary form anyway, they could be compiled at run time
> from source, so there is no executable to speak of. More corner case
> fun :)
If you are compiling them from source, and interface between the
module and the kernel is well defined (== "userspace") I guess you are
okay.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-05-07 15:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 16:42 Using GPL'd Linux drivers with non-GPL, binary-only kernel Jamie Lokier
2003-05-06 17:35 ` Alan Cox
2003-05-06 18:54 ` Jamie Lokier
2003-05-06 19:28 ` Jean-Marc Lienher
2003-05-06 19:53 ` Alan Cox
2003-05-06 22:31 ` Jamie Lokier
2003-05-06 21:38 ` Alan Cox
2003-05-08 21:36 ` Pavel Machek
2003-05-06 19:17 ` Eric W. Biederman
2003-05-06 21:55 ` Jamie Lokier
2003-05-06 22:21 ` David Schwartz
2003-05-07 8:21 ` Eric W. Biederman
2003-05-07 14:25 ` Valdis.Kletnieks
2003-05-07 14:31 ` Jamie Lokier
2003-05-07 15:50 ` Eric W. Biederman
2003-05-06 20:43 ` Pavel Machek
2003-05-06 22:18 ` Jamie Lokier
2003-05-06 21:31 ` Alan Cox
2003-05-06 22:48 ` Jamie Lokier
2003-05-07 12:20 ` Alan Cox
2003-05-07 14:26 ` Jamie Lokier
2003-05-07 15:18 ` Pavel Machek [this message]
2003-05-08 11:11 ` Krzysztof Halasa
[not found] <20030506165014$3d57@gated-at.bofh.it>
[not found] ` <20030506193019$0d29@gated-at.bofh.it>
[not found] ` <20030506220018$5b96@gated-at.bofh.it>
2003-05-07 1:17 ` Tony 'Nicoya' Mantler
[not found] <BKEGKPICNAKILKJKMHCAAEBCCLAA.Riley@Williams.Name>
2003-05-07 16:57 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 1:23 Jean Tourrilhes
2003-05-13 9:08 Dean McEwan
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=20030507151811.GC412@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.