Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <40D15BAE.1090507@f-m.fm>
Date: Thu, 17 Jun 2004 01:51:58 -0700
From: Lex Ein <lex_ein@f-m.fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: THANKS for a fantastic product
References: <40D08F9D.80701@wisc.edu>
In-Reply-To: <40D08F9D.80701@wisc.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Guy Stalnaker wrote:
 > Figure cygwin developers rarely get kudos, but here's one!

Here's another:    (Imagine Michael Moore reading this aloud:)

I'm using Cygwin for remote sshd/vnc access to a four-armed 
triple-jointed servopneumatic robotic system which could fatally stab or 
crush someone if they were standing in the wrong place during a software 
glitch.  It can also demolish the ceiling and rip itself up by the 
anchor bolts.  When the lease is up, de-installation will be easy.

For safety we decided that a water-filled moat around the machine was 
cheaper than fixing the software. Besides, the bug budget and insurance 
carrier allow one catastrophic flail/kill failure every 4 years, and 
we're only operating it for 3.

Count me one happy Cygwin user.

Next contract: medical monitoring devices.

Lex

(Relax folks, it's all true.)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/