> On Apr 28 14:40, Pach Roman (GS-EC/ESA4) * wrote:
> > Hello,
> > the following commands run properly on the c:/drive
> >  
> > c> touch yahoo
> > c> ls -l yahoo
> >    -rw-rw-rw-  1 ropach mkpasswd 0 Apr 28 13:54 yahoo
> >  
> c> chmod -w yahoo
> > c> ls -l yahoo
> >    -r--r--r--  1 ropach mkpasswd 0 Apr 28 13:54 yahoo
> >  
> > but if I try it on the u:/ drive connected over net the following error 
> > comes
> > 
> > u> ls -l yahoo
> >    -rw-r--r--  1 ropach mkpasswd 0 Apr 28 13:50 yahoo
> > u> chmod -w yahoo
> >    chmod: changing permissions of `yahoo': Permission denied
> > 
> > There were no problems up to the version cygwin-1.5.13-1.
> > The error on my machine is new for the following two versions
> >   cygwin-1.5.15-1
> >   cygwin-1.5.16-1
> 
> Did you verify that the permissions of the share is set to allow write
> access?  If the machine which exports the share you're connecting to is
> a XP or 2K3 machine, then the default shareing permissions are set to
> read only.
> Corinna
> -- 

Hi,

The u:/ drive is my working ones on the network, some kind of HOME.
I have no problems with write accesses neither using Windows2000 nor 
cygwin-1.5.13-1.
The cygwin-1.5.14-1 runs correctly as well.
It seems to me that the behavior of the chmod is combined with the some changes 
of cygwin,
made in the update from the 1.5.14-1 up to cygwin-1.5.15-1.
I have checked some other commands as well:

tmp> ls -ltr
total 1
-r--r--r--  1 ropach mkpasswd 5 Apr 29 07:13 yahoo

tmp> touch yahoo

tmp> ls -ltr
total 1
-rw-r--r--  1 ropach mkpasswd 5 Apr 29 07:14 yahoo

tmp> ls -ltr
total 1
-r--r--r--  1 ropach mkpasswd 5 Apr 29 07:14 yahoo

It is sort of strange, that the by the first call of ls the write permission is 
set.
It has been forgotten by the second one.
The touch generates no permission error either.

Roman

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

Reply via email to