All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Florian Schirmer <jolt@tuxbox.org>,
	linux-kernel@vger.kernel.org, David Turner <novalis@fsf.org>,
	andrew@mikl.as, rob@nocat.net
Subject: Re: Linksys/Cisco GPL Violations
Date: Sat, 11 Oct 2003 00:03:19 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10310102356510.12324-100000@master.linux-ide.org> (raw)
In-Reply-To: <1065854106.30987.394.camel@imladris.demon.co.uk>


David,

Your assumption is based solely on the "COLLECTIVE" issue.

Where as the application of "COMBINED" or "CONCATINATION" is not addressed
or suggested.  Suggested or implied do not cut the legal points.

The issue of "distribution" has no clear definition.

Same media?
Same box?
Same ftp site?
Same crate?
Same delivery truck?
Same warehouse?

Simple presence does not make it "distribution", in part or whole.

If you were just quoting, I would not have an issue.
I have issue of your applied meanings, which are direct result of IMHO.
The fastest way to shut me up, other than DM killfiling me to the list, is
to present a legal opinion/brief from an attorney who will back the
position.

Cheers,

Andre Hedrick
LAD Storage Consulting Group

On Sat, 11 Oct 2003, David Woodhouse wrote:

> On Fri, 2003-10-10 at 22:37 -0700, Andre Hedrick wrote:
> > David,
> > 
> > If you still have not paid and gotten legal advise on the position, you 
> > are still talking out of your ARSE. Clearly you have horses and wishes
> > confused on what GPL is and is not.
> 
> > If there is not boundary for modules then SCO will eat Linux alive in
> > court.  You can't have it both ways.
> 
> Andre, while I thank you for your well-written and coherent statement in
> opposition to my own position, I'm sure you'll agree that it doesn't
> matter what orifice I use if I stick to merely quoting...
> 
>         These requirements apply to the modified work as a whole. If
>         identifiable sections of that work are not derived from the
>         Program, and can be reasonably considered independent and
>         separate works in themselves, then this License, and its terms,
>         do not apply to those sections WHEN YOU DISTRIBUTE THEM AS
>         SEPARATE WORKS. BUT WHEN YOU DISTRIBUTE THE SAME SECTIONS AS
>         PART OF A WHOLE WHICH IS A WORK BASED ON THE PROGRAM, THE
>         DISTRIBUTION OF THE WHOLE MUST BE ON THE TERMS OF THIS LICENSE,
>         whose permissions for other licensees extend to the entire
>         whole, and thus to each and every part regardless of who wrote
>         it.
>         
>         Thus, it is not the intent of this section to claim rights or
>         contest your rights to work written entirely by you; rather, the
>         intent is to exercise the right to control the distribution of
>         derivative OR COLLECTIVE works based on the Program.
>         
> 
> -- 
> dwmw2
> 
> 


  reply	other threads:[~2003-10-11  7:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 18:22 Linksys/Cisco GPL Violations David Turner
2003-10-06  8:29 ` David Woodhouse
2003-10-10 13:09   ` Florian Schirmer
2003-10-10 13:16     ` David Woodhouse
2003-10-10 13:26       ` Florian Schirmer
2003-10-10 13:39         ` David Woodhouse
2003-10-10 14:18           ` Florian Schirmer
2003-10-10 14:25             ` David Woodhouse
2003-10-11  5:37               ` Andre Hedrick
2003-10-11  6:35                 ` David Woodhouse
2003-10-11  7:03                   ` Andre Hedrick [this message]
2003-10-13  9:40                   ` Florian Schirmer
2003-10-10 15:11     ` [Linux-bcom4301-priv] " James Stevenson
2003-10-10 15:29       ` Sasa Ostrouska
2003-10-10 16:36         ` Florian Schirmer
2003-10-10 16:58           ` Luite Stegeman
2003-10-10 15:58     ` Rob Flickenger

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=Pine.LNX.4.10.10310102356510.12324-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=andrew@mikl.as \
    --cc=dwmw2@infradead.org \
    --cc=jolt@tuxbox.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=novalis@fsf.org \
    --cc=rob@nocat.net \
    /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.