test -w broken on bash?

[Mike Thomas]

I'm running cygwin-b20 on Windows NT.  When I run the bash.exe included
in the package, I see the following behaviour:

bash% umask
000
bash% touch foo
bash% if test -w foo ; then echo foo ; fi
bash%

No echo.  The file exists, but "test -w" doesn't think it's writable.

But when I run sh.exe from the same Cygwin installation:

sh% umask
0000
sh% touch foo
sh% if test -w foo ; then echo foo ; fi
foo
sh%

The echo is there.

Is this a bug in bash or is it intended behaviour?  Does test -w have a
different meaning under bash?

--Mike

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