Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <6440EA1A6AA1D5118C6900902745938E0514F1DF@black.eng.netapp.com>
From: "Schwartz, Barry" <Barry DOT Schwartz AT netapp DOT com>
To: "'Chris Ellsworth'" <cke AT highlandshighspeed DOT net>,
   "Schwartz, Barry"
	 <Barry DOT Schwartz AT netapp DOT com>, cygwin AT cygwin DOT com
Subject: RE: Why did you guys break  EVERYTHING...
Date: Fri, 19 Apr 2002 19:29:46 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

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.  I
would much rather see the native paths.  That is definately what the old code
did and what my scripts expect.  

I definately do not need you guys to fix my scripts or show me how the programs
work.  I can handle that.  It's just that it's not how I really want to spend a
half a work day when I have other stuff to do.  I'm also a little embarrassed
since I raved about your tools and made another group adopt them for an
upcomming project.  Now, when they try to run my scripts, they will crap out...

I'll probably have to fix them since you won't be supporting the old stuff and I
need some of the tools only available in the new release.   

Although I need to tone down...  I really do "feel" the unixisms creeping in.  I
like the semantics of the unix commands and the familiarity since I work on both
platforms.  But, on a windows box (my main sqeeze) I expect paths and file
locations to take the windows form.  Just my opinion...

Thanks for getting back to me by the way.

barry


> -----Original Message-----
> From: Chris Ellsworth [mailto:cke AT highlandshighspeed DOT net]
> Sent: Friday, April 19, 2002 4:37 PM
> To: Schwartz, Barry; cygwin AT cygwin DOT com
> Subject: Re: Why did you guys break EVERYTHING...
> 
> 
> umm calm down, maybe you could post more of your scripts and what they
> do
> and expound on this line
> "What in god's name is "/usr/local/bin" on a windows machine?"
> do you mean WHERE? not what?
> 
> ----- Original Message -----
> From: "Schwartz, Barry" <Barry DOT Schwartz AT netapp DOT com>
> To: <cygwin AT cygwin DOT com>
> Sent: Friday, April 19, 2002 3:46 PM
> Subject: Why did you guys break EVERYTHING...
> 
> 
> > I'm sure you won't put this in the "intelligent" question genre
> but...
> > I've been using cygwin for years and I brag about it and make all my
> teammates install it and make my managers refuse to piss away money on
> MKS...
> > Well, I think that party's over.  I just installed the new
> distribution and every one (and I mean EVERY GODDAMN ONE) of my
> scripts that call any of your routines that need to know what a host
> or a directory are f#$king broke.  What in god's name is
> "/usr/local/bin" on a windows machine?  Why don't you UNIX weeneies
> get a grip.  F#$king fix it.  It used to be great.  Now I can't even
> change a directory.
> > I've gone back to your old, unsupported code until we can find the
> money to equip our team with MKS for $400 a throw.  Thanks for making
> a great product unusable.
> >
> > Sincerely,
> > Barry Schwartz
> >
> > --
> > 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/