public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-licensing@cygwin.com
Subject: Re: YA Licensing question
Date: Wed, 03 Dec 2008 19:04:00 -0000	[thread overview]
Message-ID: <20081203180520.GA7796@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20081203152742.GW12905@calimero.vinschen.de>

On Wed, Dec 03, 2008 at 04:27:42PM +0100, Corinna Vinschen wrote:
>
>Disclaimer:  I'm not a lawyer.  If you want to be on the safe side
>license-wise, consider to ask a lawyer specialized in software
>licensing questions for legal advice.

Ditto.  So, you really should not rely on opinions in a mailing list as
a basis for a company decision.

>Having said that...
>
>On Dec  3 09:42, Steve Duquette wrote:
>>I have looked through your FAQ's, read the GPL at least a thousand
>>times, Googled this question to death, and finally read every one of
>>the entries in the cygwin-licensing mailing list, but just can't seem
>>to find my exact case.
>>
>>I am wondering if we could just install Cygwin on to the PCs we ship as
>>part of a larger system so that we can use the NFS server.  We need NFS
>>because another part of the system is Linux based (diskless) and needs
>>to connect to the Windows host.

The reason that you need to distribute things is, of course, irrelevant
and has no bearing on the GPL.

>Why don't you just use the SMB client which is usually part of the
>Linux kernel anyway?  This allows to connect to Windows machines
>without the requirement to install Cygwin and an NFS client on the
>Windows side.

Good question.

>You don't have to reply to this question, it's just a hint that there
>are other, simpler solutions available.
>
>>We don't compile anything against Cygwin, we just would run nfsd,
>>portmap, and mountd.  Would we be legal to ship these systems with
>>Cygwin preinstalled on them?
>
>If you're installing Cygwin only to run other OSS software, like the
>NFS server, you're fine, *iff* you ship the source code of the Cygwin
>tools to your customers as well.  It's definitely *not* enough to point
>them to the Cygwin homepage.  By shipping GPL software you're
>responsible to provide your customer with the exact sources needed to
>rebuild the GPLed software.

Right and remember that "Cygwin tools" includes source code for the
cygwin DLL and any other DLLs that are required to run the tools.

This is basic GPL and it makes me wonder how you could have missed this
if you did the research that you claim to have done.  You provide source
code to any binaries that you distribute.  It's pretty simple.

      reply	other threads:[~2008-12-03 19:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 14:57 Steve Duquette
2008-12-03 15:46 ` Corinna Vinschen
2008-12-03 19:04   ` Christopher Faylor [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=20081203180520.GA7796@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin-licensing@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).