newbie chmod woes -- fixed

Paul Johnston johnston.p@worldnet.att.net
Fri Aug 20 13:46:00 GMT 1999


I just downloaded cygwin (GNU bash, version 2.02.1(2)-release
(i586-pc-cygwin32), running on NT4sp4/NTFS) -- most things working fine, but
I couldn't seem to coerce chmod to work.

$ chmod a+x myScript returns silent, but has no apparent effect.

Searched the user guide/archives, found:

$ set CYGWIN=ntea

...as possible solution, however was not successful for me.  Although $ set
| grep CYG shows the set environment variable OK, $ env | grep CYG shows
nothing.  However:

$ export CYGWIN=ntea

now shows up in $ env, and chmod is now working.  As a cygwin / bash newbie,
I don't have a good grasp why one worked and the other didn't, but at least
it worked.  So, I thought I'd post this to the list to put it in the
archives.  A better place is a 'faq-o-matic', but I don't know of one for
this project.  Would be a good idea though.

--paul




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com



More information about the Cygwin mailing list