The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Karel Kulhavy <clock@twibright.com>, linux-kernel@vger.kernel.org
Subject: Re: GPL violation by CorAccess?
Date: Wed, 20 Apr 2005 19:18:06 +0200	[thread overview]
Message-ID: <20050420171806.GB3372@elf.ucw.cz> (raw)
In-Reply-To: <20050419182529.GT17865@csclub.uwaterloo.ca>

Hi!

> > I have seen a device by CorAccess which apparently uses Linux and didn't find
> > anything that would suggest it complies to GPL, though I had access to the
> > complete shipping package. Does anyone know about known cause of violation by
> > this company or should I investigate further?
> 
> Well what is the case if you use unmodified GPL code, do you still have
> to provide sources to the end user if you give them binaries?  I would
> guess yes, but IANAL.
> 
> As far as I can tell their system is a geode GX1 so runs standard x86
> software.  Maybe they didn't have to modify any of the linux kernel to
> run what they needed.  Their applications are their business of course.
> It looks like they use QT as the gui toolkit, which I don't off hand
> know the current license conditions of.  Then there is the web browser
> and such, which has it's own license conditions.  Of course for all I
> know their user manual has an offer of sending a CD with the sources if
> you ask.  Does anyone actually have their product that could check for
> that?

QT is GPLed, IIRC. Not LGPL-ed, meaning you can't link it with
proprietary application without license from trolltech.
								Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.

      parent reply	other threads:[~2005-04-20 17:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 17:57 GPL violation by CorAccess? Karel Kulhavy
2005-04-19 18:25 ` Lennart Sorensen
2005-04-19 18:32   ` Charles Cazabon
2005-04-19 18:59     ` Chris Friesen
2005-04-19 19:19   ` Richard B. Johnson
2005-04-19 19:59     ` Chris Friesen
2005-04-19 21:44       ` Richard B. Johnson
2005-04-19 23:37         ` Chris Friesen
2005-04-20  0:26           ` Richard B. Johnson
2005-04-20  7:30           ` Bernd Petrovitsch
2005-04-20 12:49             ` Steven Rostedt
2005-04-20 12:57               ` Arjan van de Ven
2005-04-20 13:07                 ` Steven Rostedt
2005-04-20 13:36                   ` Michael Poole
2005-04-20 13:37                   ` Arjan van de Ven
2005-04-20 17:18   ` Pavel Machek [this message]

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=20050420171806.GB3372@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=clock@twibright.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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