From: Pavel Machek <pavel@suse.cz>
To: Gidon <gidon@warpcore.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel GPL Violations and How to Research
Date: Fri, 13 Feb 2004 20:02:23 +0100 [thread overview]
Message-ID: <20040213190222.GG6804@openzaurus.ucw.cz> (raw)
In-Reply-To: <1076388828.9259.32.camel@CPE-65-26-89-23.kc.rr.com>
Hi!
> So what I am writing to ask, is what is the best way to ascertain
> whether or not a binary (in this case a "kernel image" of this project)
> contains GPL'd code or functions. So far I have found nearly a hundred
> identical (down to formatting specifiers, punctuation, etc.) or nearly
> identical error messages that consistently match areas of Linux i386
> arch specific kernel code or drivers as well as matching function names,
> using the "strings" program on their Kernel image.
At this point you can be pretty sure they are violating GPL. Archive binary
they provide, and ask them for the sources.
(Drivers may come from BSD, but arch-i386 is probably not.)
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
prev parent reply other threads:[~2004-02-15 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 4:53 Gidon
2004-02-10 19:20 ` Matthew Dharm
2004-02-10 21:49 ` Gidon
2004-02-10 21:52 ` Matthew Dharm
2004-02-10 22:07 ` Gidon
2004-02-13 19:02 ` 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=20040213190222.GG6804@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=gidon@warpcore.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
all inboxes | Powered by JetHome®