From: "Raphaël Rigo LKML" <lkml@twilight-hall.net>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox + code
Date: Sun, 07 Nov 2004 20:33:55 +0100 [thread overview]
Message-ID: <418E78A3.9020500@twilight-hall.net> (raw)
In-Reply-To: <200411071227.43058.shawn.starr@rogers.com>
Shawn Starr wrote:
> I dont know if this has been brought up but, a company called sveasoft is
> blatently violating the GPL by not releasing any code:
>
> case in point:
>
> ' Talisman activation will be very simple. Just enter your Sveasoft account
> password once and it will pop up working. This even survives a full reset.
>
> This is a bummer but we have a group of folks that are not satisfied with our
> public, no-cost firmware and want to end this project so we need to adapt in
> order to survive and continue our work. I've tried to make this as simple and
> unobtrusive as possible. '
>
> Its time for the GPL authors Linux kernel, busybox and others to notify this
> 'company' that they are violating the GPL. You cannot revoke existing GPL
> code with a different license.
>
> If Linksys had to release the code Sveasoft must follow suit.
>
> Shawn.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Hello,
I think you are wrong, just check this page :
http://www.sveasoft.com/modules/phpBB2/viewtopic.php?t=3033
My 2 cents,
Raphaël Rigo
next prev parent reply other threads:[~2004-11-07 19:33 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 17:27 Shawn Starr
2004-11-07 19:33 ` Raphaël Rigo LKML [this message]
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
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=418E78A3.9020500@twilight-hall.net \
--to=lkml@twilight-hall.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.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
Powered by JetHome