public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Diego Calleja <diegocg@gmail.com>
Cc: Chris Wedgwood <cw@f00f.org>,
	jmerkey@wolfmountaingroup.com, rostedt@goodmis.org,
	mrmacman_g4@mac.com, legal@lists.gnumonks.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	garbageout@sbcglobal.net
Subject: Re: blatant GPL violation of ext2 and reiserfs filesystem drivers
Date: Fri, 23 Dec 2005 04:30:07 +0100	[thread overview]
Message-ID: <20051223033007.GJ27525@stusta.de> (raw)
In-Reply-To: <20051223041522.ac36635d.diegocg@gmail.com>

On Fri, Dec 23, 2005 at 04:15:22AM +0100, Diego Calleja wrote:
> El Thu, 22 Dec 2005 18:56:38 -0800,
> Chris Wedgwood <cw@f00f.org> escribió:
> 
> > That's entirely debatable and I would recommend the original poster
> > seek legal advice on this as there are many people who will claim
> > loading GPLd modules is paramount to linking and therefore this is a
> > violation.
> 
> So, a GPL application running on top of a BSD-licensed kernel
> (or library) is illegal? I doubt it...

application != kernel module

And your example would anyways not be a problem since GPL + BSD = GPL
(assuming the 3 clause BSD licence).

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2005-12-23  3:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22 16:08 blatant GPL violation of ext2 and reiserfs filesystem drivers Robert W. Fuller
2005-12-22 18:01 ` Kyle Moffett
2005-12-22 20:27   ` Steven Rostedt
2005-12-22 23:12     ` Jeff V. Merkey
2005-12-23  2:56       ` Chris Wedgwood
2005-12-23  3:15         ` Diego Calleja
2005-12-23  3:28           ` Chris Wedgwood
2005-12-23  3:38             ` Steven Rostedt
2005-12-23  3:49               ` Matthew Wilcox
2005-12-23  4:25               ` Jamie Lokier
2005-12-23  3:30           ` Adrian Bunk [this message]
2005-12-23 15:35     ` Ben Slusky
2005-12-23 19:34       ` Bryan Henderson
2005-12-23 20:16         ` Scott Mansfield
2005-12-23 22:00           ` Bryan Henderson
2005-12-24  1:48           ` Horst von Brand
2005-12-24  2:41             ` Peter Williams
2005-12-24  3:25             ` Jamie Lokier
2006-01-04 11:09       ` Harald Welte
2006-01-04 11:54         ` Jamie Lokier
2006-01-04 13:18           ` Harald Welte
2006-01-04 13:46             ` Matthew Wilcox
2006-01-04 17:46               ` Harald Welte
2006-01-04 23:03               ` Gene Heskett
2006-01-04 22:43                 ` Jeff V. Merkey
2006-01-04 14:16             ` Jamie Lokier
2006-01-04 14:45               ` Matthew Wilcox
2006-01-04 15:57                 ` Jamie Lokier
2006-01-04 17:42                 ` Harald Welte
2006-01-05 17:52                 ` Bryan Henderson

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=20051223033007.GJ27525@stusta.de \
    --to=bunk@stusta.de \
    --cc=cw@f00f.org \
    --cc=diegocg@gmail.com \
    --cc=garbageout@sbcglobal.net \
    --cc=jmerkey@wolfmountaingroup.com \
    --cc=legal@lists.gnumonks.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=rostedt@goodmis.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