From: "Peter A. Castro" <doctor@fruitbat.org>
To: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Can MKS Toolkit and Cygwin safely co-exist on Windows servers?
Date: Fri, 20 Nov 2015 19:25:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1511201121200.3276@ming.fruitbat.org> (raw)
In-Reply-To: <6CF2FC1279D0844C9357664DC5A08BA21BC2DE1A@msgb09.nih.gov>
On Wed, 18 Nov 2015, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> Date: Wed, 18 Nov 2015 21:29:30 +0000
> From: "Buchbinder, Barry (NIH/NIAID) [E]"
> Subject: RE: Can MKS Toolkit and Cygwin safely co-exist on Windows servers?
>
> Peter A. Castro sent the following at Monday, November 16, 2015 9:17 PM
>>
>> Oh! I've been there and tried to do that but was shutdown for corporate
>> policy reasons. Remember that business wants someone to shoot at when
>> things break. That license you have for MKS means your company can
>> demand support from someone. Cygwin is "free" and support is really just
>> this email list and "WJM". :)
>
> I believe that paid support is available from Red Hat.
>
> http://www.redhat.com/services/custom/cygwin/
Oh! I did not know about that! That is cool! Wish I'd known about that
a few years ago!!
(I presume that "professional support" is Corinna? :)
> - Barry
--
--=> Peter A. Castro
Email: doctor at fruitbat dot org / Peter dot Castro at oracle dot com
"Cats are just autistic Dogs" -- Dr. Tony Attwood
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2015-11-20 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 0:54 Kenneth Wolcott
2015-11-17 1:00 ` Warren Young
2015-11-17 2:17 ` Peter A. Castro
2015-11-18 21:30 ` Buchbinder, Barry (NIH/NIAID) [E]
2015-11-20 19:25 ` Peter A. Castro [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=alpine.LNX.2.00.1511201121200.3276@ming.fruitbat.org \
--to=doctor@fruitbat.org \
--cc=BBuchbinder@niaid.nih.gov \
--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).