From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: "Michael Poole" <mdpoole@troilus.org>,
"Kyle Moffett" <mrmacman_g4@mac.com>,
=?utf-8?q?Raphaël Rigo LKML?= <lkml@twilight-hall.net>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
davids@webmaster.com,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox +code
Date: Wed, 10 Nov 2004 16:11:11 -0500 [thread overview]
Message-ID: <419283EF.8050708@tmr.com> (raw)
In-Reply-To: <200411092328.16426.dtor_core@ameritech.net>
Dmitry Torokhov wrote:
> On Tuesday 09 November 2004 11:14 pm, Michael Poole wrote:
> http://www.sveasoft.com/modules/phpBB2/viewtopic.php?t=3868
>
>
>>Post subject: I am a Sveasoft subscriber, can I redistribute?
>>...
>>The policy for pre-release firmware is different. You may choose to
>>redistribute only those portions of pre-release firmware specifically
>>covered by the GPL license. Those portions of the distribution that are
>>separate additions developed by Sveasoft as part of a pre-release
>>distribution may not be re-distributed. Redistribution of pre-release
>>firmware that includes Sveasoft's non-GPL code will result in the
>>termination of your subscription.
>>
>
>
> So it looks like they are in clear, unless those separate additions are
> derived from GPLed software.
>
That web page seems pretty clear... some parts of the prerelease are
non-GPL, you can distribute the GPL code as usual. Unless there is aome
claim that the non-GPL parts are derived from GPL original source or
contain GPL code, why shouldn't they restrict the distribution of their
own code?
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-11-10 21:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 17:27 GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox + code Shawn Starr
2004-11-07 19:33 ` Raphaël Rigo LKML
2004-11-07 19:38 ` Shawn Starr
2004-11-07 21:16 ` Daniel Egger
2004-11-08 1:14 ` David Schwartz
2004-11-08 14:56 ` Pedro Venda (SYSADM)
2004-11-08 20:53 ` David Schwartz
2004-11-08 15:24 ` Alan Cox
2004-11-08 19:57 ` Geert Uytterhoeven
2004-11-08 21:33 ` Pedro Venda (SYSADM)
2004-11-08 21:54 ` David Schwartz
2004-11-08 23:25 ` Alan Cox
2004-11-08 20:53 ` GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox +code David Schwartz
2004-11-08 23:00 ` Alan Cox
2004-11-09 2:32 ` Dmitry Torokhov
2004-11-09 4:08 ` David Rees
2004-11-09 4:23 ` Dmitry Torokhov
2004-11-09 9:47 ` Alan Cox
2004-11-09 19:30 ` David Schwartz
2004-11-09 19:45 ` Chris Friesen
2004-11-09 20:23 ` David Schwartz
2004-11-09 20:48 ` Valdis.Kletnieks
2004-11-09 23:06 ` Alan Cox
2004-11-10 1:47 ` David Schwartz
2004-11-10 9:27 ` Geert Uytterhoeven
2004-11-10 18:14 ` Alan Cox
2004-11-10 19:32 ` Valdis.Kletnieks
2004-11-10 20:09 ` Stuart MacDonald
2004-11-10 21:18 ` Trever L. Adams
2004-11-09 23:22 ` Alan Cox
2004-11-10 1:34 ` Kyle Moffett
2004-11-10 2:01 ` Michael Poole
2004-11-10 3:02 ` Kyle Moffett
2004-11-10 4:14 ` Michael Poole
2004-11-10 4:28 ` Dmitry Torokhov
2004-11-10 21:11 ` Bill Davidsen [this message]
2004-11-10 23:09 ` Kyle Moffett
2004-11-10 22:14 ` Alan Cox
2004-11-15 14:47 ` David Woodhouse
2004-11-10 23:26 ` Dmitry Torokhov
2004-11-10 5:07 ` David Schwartz
2004-11-10 1:47 ` David Schwartz
2004-11-12 17:04 ` Horst von Brand
2004-11-09 21:13 ` Stuart MacDonald
2004-11-09 2:23 ` GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox + code Paul Jakma
2004-11-10 10:21 ` David Woodhouse
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=419283EF.8050708@tmr.com \
--to=davidsen@tmr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@twilight-hall.net \
--cc=mdpoole@troilus.org \
--cc=mrmacman_g4@mac.com \
/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).