Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
content-class: urn:content-classes:message
Subject: RE: Why did you guys break  EVERYTHING...
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Sat, 20 Apr 2002 12:58:28 +1000
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5E90@itdomain003.itdomain.net.au>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Schwartz, Barry" <Barry.Schwartz@netapp.com>,
   "Chris Ellsworth" <cke@highlandshighspeed.net>, <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit


> -----Original Message-----
> From: Schwartz, Barry [mailto:Barry.Schwartz@netapp.com] 
> Sent: Saturday, April 20, 2002 12:30 PM
> To: 'Chris Ellsworth'; Schwartz, Barry; cygwin@cygwin.com
> Subject: RE: Why did you guys break EVERYTHING...
> 
> 
> OK.  Feeling better now... If one of my customers wrote me 
> that with no examples, I'd get a kick out of it too. So... 
> rsh must have changed.  I use it in a script to move perforce 
> clients around from NT to UNIX. The attached script, 
> getfull.pl is the example that failed with the new program 
> and worked with the old.
> 
> Also, the semantics and output of "which", "ls", and "cp" 
> have changed too in my opinion, not the least of which is the 
> fau root directory and all the cygnus stuff being in 
> "/usr/local/bin" which is not a real directory on my machine. 

The cygnus stuff goes into c:\cygwin\bin aka /usr/bin, not
/usr/local/bin. Are you sure you installed Cygwin via setup.exe, not
from some other site?

As for the tools, by and large they all support d:\foo syntax as well -
but remember, if you run them within bash, the \ becomes an escape
character, so you need d:\\foo for the tool to see the backslash.

Rob

--
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/