mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Stephen Pollei" <stephen.pollei@gmail.com>,
	"Lee Revell" <rlrevell@joe-job.com>
Cc: <mmoneta@optonline.net>, <linux-kernel@vger.kernel.org>,
	<andersen@codepoet.org>
Subject: RE: ZyXEL Kernel /BusyBox GPL violation?
Date: Tue, 26 Jul 2005 09:15:31 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKEEDMFHAB.davids@webmaster.com> (raw)
In-Reply-To: <feed8cdd050725224213df2d11@mail.gmail.com>


> > Also if they didn't modify the kernel, they don't have to give you
> > source, they can just refer you to kernel.org.
>
> Wrong.....
>
> http://www.fsf.org/licensing/licenses/gpl-faq.html#DistributeWithS
> ourceOnInternet
> [[[I want to distribute binaries without accompanying sources. Can I
> provide source code by FTP instead of by mail order?
>     You're supposed to provide the source code by mail-order on a
> physical medium, if someone orders it. You are welcome to offer people
> a way to copy the corresponding source code by FTP, in addition to the
> mail-order option, but FTP access to the source is not sufficient to
> satisfy section 3 of the GPL.
>
>     When a user orders the source, you have to make sure to get the
> source to that user. If a particular user can conveniently get the
> source from you by anonymous FTP, fine--that does the job. But not
> every user can do such a download. The rest of the users are just as
> entitled to get the source code from you, which means you must be
> prepared to send it to them by post.
>
>     If the FTP access is convenient enough, perhaps no one will choose
> to mail-order a copy. If so, you will never have to ship one. But you
> cannot assume that.
>
>     Of course, it's easiest to just send the source with the binary in
> the first place. ]]]

	I'm sorry, this makes no sense. What if a user can't conveniently get the
source by mail?

	More users can more conveniently get the source by HTTP than can get it by
mail. This argument may have made sense many years ago, but it doesn't now.

	The GPL does not say you have to mail it. The GPL says you have to provide
it "on a medium customarily used for software interchange". That means *YOU*
get to pick the medium, you just can't pick one that's so obscure that
nobody could decode it. The web is just such a medium.

	DS



  reply	other threads:[~2005-07-26 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26  3:21 Mace Moneta
2005-07-26  3:28 ` Lee Revell
2005-07-26  5:42   ` Stephen Pollei
2005-07-26 16:15     ` David Schwartz [this message]
2005-07-26 17:07       ` linux-os (Dick Johnson)
2005-07-26 17:43         ` Mace Moneta

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=MDEHLPKNGKAHNMBLJOLKEEDMFHAB.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmoneta@optonline.net \
    --cc=rlrevell@joe-job.com \
    --cc=stephen.pollei@gmail.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

all inboxes | Powered by JetHome®