All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: jmerkey@wolfmountaingroup.com, linux-kernel@vger.kernel.org
Subject: Re: [REQUEST] Clarification from Copyright Holders on FUSE/NDISWRAPPER
Date: Sun, 28 Sep 2008 19:46:16 -0400	[thread overview]
Message-ID: <20080928194616.10d25760@bree.surriel.com> (raw)
In-Reply-To: <20080928194536.GC8711@mit.edu>

On Sun, 28 Sep 2008 15:45:36 -0400
Theodore Tso <tytso@mit.edu> wrote:

> The position statement on closed-source Linux Kernel Modules was
> deliberately not a "policy statement", nor did it talk about issues
> about what is or isn't legal.  This was deliberate.  Issues over
> whether or not the GPL covers binary modules fundamentally depend on
> individual legal jurisdictions' interpretations of copyright law and
> derivitive works, 

This, of course, means you may want to ask your lawyer to
make sure to which countries binary only kernel modules can
be distributed and in which countries they are definately
illegal.

Then you can put some access control in place on your web
site to make sure people from countries where binary only
kernel modules are illegal cannot download your drivers.

Of course, what to do with the countries where the answer
to the question is not clear cut is up to you...

Investigating a few hundred jurisdictions could be a fair
amount of work, but if you want to be absolutely sure there's
not much else you can do.

-- 
All rights reversed.

  parent reply	other threads:[~2008-09-28 23:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28 17:15 [REQUEST] Clarification from Copyright Holders on FUSE/NDISWRAPPER jmerkey
2008-09-28 19:45 ` Theodore Tso
2008-09-28 19:24   ` jmerkey
2008-09-28 23:46   ` Rik van Riel [this message]
2008-09-28 23:34     ` jmerkey
2008-09-29  1:57       ` Theodore Tso
2008-09-29  3:27         ` jmerkey
2008-09-30  4:06           ` Eric W. Biederman
2008-09-30  4:18             ` jmerkey
2008-10-05 10:12           ` Pavel Machek

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=20080928194616.10d25760@bree.surriel.com \
    --to=riel@redhat.com \
    --cc=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.