From: Chris Faylor <cgf@cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: Cygwin CD licensing?
Date: Tue, 11 Apr 2000 14:09:00 -0000 [thread overview]
Message-ID: <20000411170919.J2717@cygnus.com> (raw)
In-Reply-To: <200004112103.RAA23959@envy.delorie.com>
On Tue, Apr 11, 2000 at 05:03:50PM -0400, DJ Delorie wrote:
>> But the more important question, usually answered by a license, is
>> what can our customer do with a single copy of the CD? Can you
>> install it on exactly one machine? Do you need one copy per user?
>> Can you install it on multiple machines from a single CD?
>
>I believe the CD is site-licensed, so each customer can install it on
>as many of *their* machines as they want. The installer is not free,
>but the software it installs is, so once it's installed there isn't
>any proprietary software on the PC anyway, so what's stopping them
>from installing it elsewhere also?
I've forwarded this to the people at Cygnus/Red Hat who answer this kind
of question on a daily basis.
In case anyone's interested, you can send email to 'cygwin-info@cygnus.com'
if you have licensing related questions.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-04-11 14:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-07 11:24 why is make so bloody slow (for me) Kevin Layer
2000-04-07 14:20 ` Corinna Vinschen
2000-04-07 14:26 ` Corinna Vinschen
2000-04-07 14:51 ` Kevin Layer
2000-04-07 16:10 ` Corinna Vinschen
2000-04-07 16:54 ` Kevin Layer
2000-04-07 16:56 ` Kevin Layer
2000-04-07 17:04 ` Kevin Layer
2000-04-07 17:05 ` Kevin Layer
2000-04-11 13:51 ` Cygwin CD licensing? Keith Graham
2000-04-11 14:04 ` DJ Delorie
2000-04-11 14:09 ` Chris Faylor [this message]
2000-04-09 12:06 ` why is make so bloody slow (for me) David Deaven
2000-04-10 12:37 ` Kevin Layer
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=20000411170919.J2717@cygnus.com \
--to=cgf@cygnus.com \
--cc=cygwin@sourceware.cygnus.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).