From: Ben Greear <greearb@candelatech.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: jw schultz <jw@pegasys.ws>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: over&out (Re: feature request - why not make netif_rx() a pointer?)
Date: Thu, 24 Oct 2002 00:08:41 -0700 [thread overview]
Message-ID: <3DB79C79.9050200@candelatech.com> (raw)
In-Reply-To: 1035440743.9164.24.camel@gby.benyossef.com
Gilad Ben-Yossef wrote:
> IANAL but AFAIK the GPL V2 requires you to either distribute the
> source/patch together with the binary or include a *written* obligation
> valid for three years to supply the sources to any thrid party.
>
> So, for example, if you disribute the binary on a CD, or some embedded
> device, sticking the patch somewhere on your web site with an obscure
> link pointing to them is technicaly a violation of the GPL.
You could hide the source in the documentation, no one ever reads that ;)
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-10-24 7:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 0:39 feature request - why not make netif_rx() a pointer? Jean Tourrilhes
2002-10-23 13:39 ` Slavcho Nikolov
2002-10-23 14:03 ` Chris Friesen
2002-10-23 16:23 ` over&out (Re: feature request - why not make netif_rx() a pointer?) Slavcho Nikolov
2002-10-23 22:59 ` jw schultz
2002-10-24 6:25 ` Gilad Ben-Yossef
2002-10-24 7:08 ` Ben Greear [this message]
2002-10-25 11:50 ` Adrian Bunk
2002-10-23 16:48 ` feature request - why not make netif_rx() a pointer? Jean Tourrilhes
2002-10-23 17:27 ` Ben Greear
2002-10-24 4:13 ` David S. Miller
2002-10-24 9:28 ` Henning P. Schmiedehausen
2002-10-24 10:15 ` David S. Miller
2002-10-24 11:01 ` Henning Schmiedehausen
2002-10-24 13:30 ` Slavcho Nikolov
2002-10-24 13:46 ` David S. Miller
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=3DB79C79.9050200@candelatech.com \
--to=greearb@candelatech.com \
--cc=gilad@benyossef.com \
--cc=jw@pegasys.ws \
--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;
as well as URLs for NNTP newsgroup(s).