public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brian F. G. Bidulock" <bidulock@openswitch.org>
To: linux-kernel@vger.kernel.org
Subject: Re: GPL Question
Date: Fri, 27 Oct 2000 16:08:07 -0500	[thread overview]
Message-ID: <20001027160807.B7036@openswitch.org> (raw)
In-Reply-To: <NCBBLIEPOCNJOAEKBEAKMEJFLIAA.davids@webmaster.com> <Pine.LNX.4.10.10010272013140.13264-100000@dax.joh.cam.ac.uk>
In-Reply-To: <Pine.LNX.4.10.10010272013140.13264-100000@dax.joh.cam.ac.uk>; from jas88@cam.ac.uk on Fri, Oct 27, 2000 at 08:17:11PM +0100

All, IANAL, but:

    #1: take this discussion of this list...

    goto news:comp.software.licensing

    read the FAQ

    if you still have questions send them to mailto:licensing@gnu.org

    if you don't like any of those answers, talk to a lawyer

    be fair, don't steal someone else's work (don't be like Dennis)

    both GPL and LGPL are clear: you change it, you publish source

    if you don't want to publish source, best bet is don't change it,
        just use it the way it is

    you may not have the right to change anything (according to your
        employer): consult a lawyer

--Brian

On Fri, 27 Oct 2000, James Sutherland wrote:

> On Fri, 27 Oct 2000, David Schwartz wrote:
> 
> > 
> > > Now, if a module is loaded that registers a set of functions that have
> > > increased functionality compared to the original functions, if that
> > > modules is not based off GPL'd code, must the source code of that module
> > > be released under the GPL?
> > 
> > 	If the answer to this is "yes", then Microsoft should own some rights to
> > every piece of software that uses the Windows API.
> 
> In fact, since you call the Windows API by linking against Windows
> libraries (kernel32.dll etc), Microsoft have as much right to dictate the
> licensing of Windows apps as the FSF has to require apps linked against
> GPLed code to be GPLed. (IMO, neither has any such right; of course, given
> the spate of recent laws we've seen, I wouldn't put any faith in a legal
> system to reach the "right" decision...)
> 
> In this particular case - just communicating with GPLed code - the answer
> is no, you are not required to impose GPL restrictions on your users, you
> can use a free license instead (or a proprietary one, if you really
> want...)
> 
> 
> James.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

-- 
Brian F. G. Bidulock
http://www.openss7.org/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-27 21:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 16:36 GPL Question Jason Wohlgemuth
2000-10-27 16:31 ` David Weis
2000-10-27 17:21   ` Alan Cox
2000-10-27 17:26     ` Matthew Dharm
2000-10-27 17:56       ` Somewhat different " Christopher Friesen
2000-10-27 18:06         ` Rik van Riel
2000-10-27 20:49           ` Alan Cox
2000-10-27 17:16 ` Mark Salisbury
2000-10-27 17:23 ` Alan Cox
2000-10-27 18:53 ` David Schwartz
2000-10-27 18:56   ` Rik van Riel
2000-10-27 20:53     ` Alan Cox
2000-10-27 19:17   ` James Sutherland
2000-10-27 21:08     ` Brian F. G. Bidulock [this message]
2000-10-27 20:52   ` Alan Cox
2000-10-30 12:27     ` Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2004-06-28 22:13 GPL question ca_tex-kernel
2004-06-29 11:01 ` David Weinehall

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=20001027160807.B7036@openswitch.org \
    --to=bidulock@openswitch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox