linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jamie Lokier <jamie@shareable.org>
Cc: Pavel Machek <pavel@ucw.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Using GPL'd Linux drivers with non-GPL, binary-only kernel
Date: 06 May 2003 22:31:14 +0100	[thread overview]
Message-ID: <1052256672.1983.174.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030506221819.GC6284@mail.jlokier.co.uk>

On Maw, 2003-05-06 at 23:18, Jamie Lokier wrote:
> If I load a Java class into a Java VM, that class is executing in the
> VM's "userspace", even though both the class and VM execute together
> in the underlying kernel's userspace.  If I load an Emacs Lisp library
> into Emacs, that's ok too in the same way.

Thats not actually clear either. The kernel contains the clear syscall
message for good reasons. The GPL itself talks about stuff that comes
normally with the OS very carefully for similar reasons.

You see there isn't any difference between an interpreter hitting
	Java bytecode 145
and a function call of 
	perform_java_bytecode(145);

Indeed the JVM may turn one into the other.


If you think that is bad remember that the DMCA and other rulings have
held shrink wrap licenses can sometimes overrule US style "fair use", so
your JVM in JITting code may be making you liable for a license
violation for some applications.

Corner cases are fun in more than just the computing profession 8)



  reply	other threads:[~2003-05-06 22:17 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 [this message]
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
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
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=1052256672.1983.174.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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).