public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Silva <r3pek@r3pek.homelinux.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Possible GPL Violation
Date: Mon, 30 May 2005 16:19:42 +0100	[thread overview]
Message-ID: <1117466382.12693.19.camel@localhost> (raw)
In-Reply-To: <yw1x1x7olq87.fsf@ford.inprovide.com>

On Mon, 2005-05-30 at 16:53 +0200, Måns Rullgård wrote:
> Carlos Silva <r3pek@r3pek.homelinux.org> writes:
> 
> >> > The thing is that i asked for the kernel source they use in the
> >> > system and they said they can't give it since they have some
> >> > proprietary code in it, as far as i understood.
> >> 
> >> If they use some modules of their own writing, the general agreement
> >> seems to be that they don't need to release the source code to those.
> >> They should still give you the kernel source they used, along with any
> >> patches they may have applied.
> >
> > I know this too. The thing is that they don't give me anything. They
> > only sell me the appliance, nothing more. :(
> 
> All too common.  You should begin by kindly pointing out what their
> obligations are, and if they fail to comply, switch to a harsher tone,
> and post your correspondence in a public place.  I'm not certain that
> lkml is the proper place for this, but it may be the only place we
> have.  If all else fails, slashdot them.  That will probably also
> fail, but at least you can enjoy watching other people call them
> names.
I don't think that's the way to go... i aslready asked them in kindly
and harsher tone, so it's a dead end here.

> 
> >> > I really don't know the proper way to report a GPL violation so i
> >> > thought this was a good place.  If there is any question please feel
> >> > free to ask, i'll do my best to answer it.
> >> 
> >> I'm having some problems myself with an STB manufacturer (Amino).  The
> >> STB is running a Busybox/Montavista Linux of some kind, and I need to
> >> make some changes.  To do this, they tell me I need the SDK, which is
> >> only available under NDA, and then only after purchasing a support
> >> contract for an ungodly number of dollars.  Somehow, I get the feeling
> >> they are on thin ice here.
> >> 
> > Panda uses debian in this appliance ;)
> 
> That's a bit ironic, considering that Debian are among those tappreciatedhat take
> the "freedom" thing most seriously.  Maybe you can get some ideas from
> the debian-legal list.
> 
Probably they can point me to somewhere, but if someone in here knows
what should be done, i'll be appreciated.


  reply	other threads:[~2005-05-30 15:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 13:19 Possible GPL Violation Carlos Silva
2005-05-30 13:50 ` Måns Rullgård
2005-05-30 14:11   ` Carlos Silva
2005-05-30 14:53     ` Måns Rullgård
2005-05-30 15:19       ` Carlos Silva [this message]
2005-05-30 15:42         ` Giuseppe Bilotta
  -- strict thread matches above, loose matches on Subject: below --
2004-03-26 16:08 possible GPL violation Warren Turkal

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=1117466382.12693.19.camel@localhost \
    --to=r3pek@r3pek.homelinux.org \
    --cc=linux-kernel@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