From: Jarek Poplawski <jarkao2@gmail.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: Brad Doctor <brad.doctor@gmail.com>,
netdev@vger.kernel.org, Luca Deri <deri@ntop.org>
Subject: Re: [OT] ntop / GPL (was Re: PF_RING: Include in main line kernel?)
Date: Mon, 19 Oct 2009 05:55:21 +0000 [thread overview]
Message-ID: <20091019055521.GA5948@ff.dom.local> (raw)
In-Reply-To: <20091018124706.GG27747@prithivi.gnumonks.org>
On Sun, Oct 18, 2009 at 02:47:06PM +0200, Harald Welte wrote:
> Hi Jarek, Brad, Luca,
>
> [putting my gpl-violations.org hat on]
>
> On Wed, Oct 14, 2009 at 06:46:11PM +0200, Jarek Poplawski wrote:
> > Brad Doctor wrote, On 10/14/2009 04:33 PM:
> >
> > > Download ntop
> > >
> > > ntop is distributed under the GNU GPL. In order to be entitled to download
> > > ntop you must accept the GNU license.
> >
> > I can't find such a thing neither in GNU GPL v2:
>
> This is true. The GPL does never need to be accepted for mere use (i.e.
> running) the program. This is at least true for the continental european
> copyright systems, where any legally obtained copy of a program implicitly
> carries the permission for running the program. Only for any other activity
> you will need to accept the license.
>
> but, like others posted in this thread, ntop is not the PF_RING code.
ntop doesn't matter here at all:
if ((X uses the stock GPL license.) &&
(Y is distributed under the GNU GPL) &&
(In order to be entitled to download Y
you must accept the GNU license.) &&
(The GPL does never need to be accepted for mere use.))
is logically false.
BTW, legal systems don't matter here at all.
Jarek P.
next prev parent reply other threads:[~2009-10-19 5:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 14:33 PF_RING: Include in main line kernel? Brad Doctor
2009-10-14 16:01 ` Stephen Hemminger
2009-10-14 17:02 ` Brad Doctor
2009-10-14 19:33 ` Stephen Hemminger
2009-10-14 20:17 ` Luca Deri
2009-10-14 20:27 ` David Miller
2009-10-15 0:25 ` Eric Dumazet
2009-10-14 20:36 ` Evgeniy Polyakov
2009-10-14 21:27 ` Ben Greear
2009-10-14 21:34 ` Luca Deri
2009-10-14 21:49 ` David Miller
2009-10-14 23:29 ` Ben Greear
2009-10-15 7:02 ` Evgeniy Polyakov
2009-10-15 7:22 ` David Miller
2009-10-15 16:33 ` Ben Greear
2009-10-18 12:45 ` Harald Welte
2009-10-18 12:43 ` Harald Welte
2009-10-18 14:18 ` Evgeniy Polyakov
2009-10-14 16:46 ` Jarek Poplawski
2009-10-14 17:02 ` Brad Doctor
2009-10-14 17:18 ` Jarek Poplawski
2009-10-18 12:47 ` [OT] ntop / GPL (was Re: PF_RING: Include in main line kernel?) Harald Welte
2009-10-19 5:55 ` Jarek Poplawski [this message]
2009-10-19 7:12 ` Jarek Poplawski
2009-10-14 18:19 ` PF_RING: Include in main line kernel? Brent Cook
2009-10-14 19:54 ` Luca Deri
2009-10-14 20:15 ` David Miller
2009-10-14 20:26 ` Luca Deri
2009-10-14 20:29 ` David Miller
2009-10-14 20:34 ` Luca Deri
2009-10-14 20:50 ` Mark Smith
2009-10-18 12:56 ` Harald Welte
2009-10-18 12:50 ` Harald Welte
2009-10-18 14:50 ` Evgeniy Polyakov
2009-10-15 7:35 ` Rémi Denis-Courmont
2009-10-18 12:38 ` Harald Welte
2009-10-18 17:37 ` Luca Deri
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=20091019055521.GA5948@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=brad.doctor@gmail.com \
--cc=deri@ntop.org \
--cc=laforge@gnumonks.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).