From: Elizabeth Barham <soggytrousers@yahoo.com>
To: cygwin@cygwin.com
Subject: Re: Is Cygwin legal under Windows XP?
Date: Sun, 21 Apr 2002 18:35:00 -0000 [thread overview]
Message-ID: <87n0vwlf0m.fsf@liliwhite.renaissance.oasis> (raw)
In-Reply-To: "Michael D. Crawford"'s message of "Sun, 21 Apr 2002 19:50:03 -0500"
This whole thing seems kind of iffy in regards to Microsoft's
position. While Microsoft has some authority, consumers do too and
Windows XP's EULA may violate some consumer rights (I don't know of
any off hand, though). But even if it doesn't violate any at the
moment, it violates what I consider my own "consumer rights" - I have
the right to run any program I want to on any computer I own,
including Microsoft Operating Systems.
And what is this EULA anyway? If I purchase software, do I or do I not
own the software? And can I or can I not do anything I want to with it
- I mean, it's mine and they sold it to me. Or am I "leasing" the
software from someone?
It's one thing for an EULA to say, "You may have one copy of this
piece of software running on at most one computer at any time," but
another thing for it to say what I can use the software for.
Elizabeth
"Michael D. Crawford" <crawford@goingware.com> writes:
> Another issue is the number of clients served by a windows host
> running cygwin.
> I remember that was an issue for O'Reilly for the web server they
> used to sell for Windows - non-server versions of Windows were only
> licensed to serve a few clients of any sort, and server versions of
> windows that could have any number of users came bundled with IIS, so
> O'Reilly was unable to sell to people who already had a bundled web
> server.
>
> If somebody's running cygwin on a machine that's only licensed as a
> desktop version of windows, and they have a lot of clients for apache,
> postgresql, ssh or whatnot, they're likely in violation of the windows
> license.
>
> I couldn't say whether the cygwin developers could be held liable by
> microsoft for not enforcing the desktop client limit.
>
> Michael D. Crawford GoingWare Inc. - Expert Software Development and
> Consulting http://www.goingware.com/ crawford@goingware.com
>
> Tilting at Windmills for a Better Tomorrow.
>
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-04-22 1:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"Michael D. Crawford"'s message of "Sun, 21 Apr 2002 19:50:03 -0500">
2002-04-21 18:05 ` Michael D. Crawford
2002-04-21 18:35 ` Elizabeth Barham [this message]
2002-04-21 18:44 ` Bruce Williams
2002-04-21 23:31 ` Charles Wilson
2002-04-22 7:14 ` Randall R Schulz
2002-04-22 13:18 ` Chris January
2002-04-21 4:18 Robert Collins
2002-04-21 4:35 ` Sam Edge
2002-04-21 5:49 ` Bruce Williams
-- strict thread matches above, loose matches on Subject: below --
2002-04-20 23:32 Doug Wyatt
2002-04-21 0:56 ` Gerrit P. Haase
2002-04-21 3:05 ` Sam Edge
2002-04-21 3:31 ` Doug Wyatt
2002-04-21 3:34 ` Sam Edge
2002-04-21 4:45 ` Bruce Williams
2002-04-21 17:05 ` Gary R. Van Sickle
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=87n0vwlf0m.fsf@liliwhite.renaissance.oasis \
--to=soggytrousers@yahoo.com \
--cc=cygwin@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).