> chmod in cygwin is not working. I did the following:
>
> mkdir mybin
> gvim mybin/vi
> ... /* mybin vi just does a gvim */
> chmod +x mybin/vi
> -rw-r---r-- 1 default unknown 9 jun 18 13:11
>
> (There is a mybin/vi at the end but in this
chmod in cygwin is not working. I did the following:
mkdir mybin
gvim mybin/vi
... /* mybin vi just does a gvim */
chmod +x mybin/vi
-rw-r---r-- 1 default unknown 9 jun 18 13:11
(There is a mybin/vi at the end but in this message
it wouldn't fit on the line).
Sorry bug-fileutils, I don't think this is your problem.
On Monday 4 Feb 02, John Miller writes:
>
> I hope this isn't a stupid question. When I try to use chmod, it doesn't do
> what I expect.
> See below. Am I doing something wrong? I'm running Windows NT 4.0 sp6. I've
> tried with Windows 2
I hope this isn't a stupid question. When I try to use chmod, it doesn't do
what I expect.
See below. Am I doing something wrong? I'm running Windows NT 4.0 sp6. I've
tried with Windows 2000 with same results.
Thanks
-John
administrator@WASHINGTON /test
$ ls -l
total 1
-rw-r--r-- 1 adminis
>chmod -v +x filename
> And the diagnostic information report the perssion of file has been
> changed,but when use 'll' to view the file not found the change!
Thank you for your bug report. However on this bug list we are ill
prepared to deal with Cygwin difficulties. I don't think anyone o
Usage:
chmod -v +x filename
And the diagnostic information report the perssion of
file has been changed,but when use 'll' to view the file not found the
change!
thank you!!
Hi,
I just downloaded cygwin 1.1.4, it succesfully
installed and seems to work fine with some exception.
When I try to make a file executable it just does not
happen. I tried both u+x and 700, none of them seems
to have any effect on the file.
Any suggestions?
Thank you,
Daniela
__
I've been working with the Cygwin bash shell and using the chmod command but
something strange is happening...
When I create a file and change the mode using the -c flag it says that the
mode has been changed but when the ls -l command is envoked, the permissions
have stayed the same...
EXAMPLE:
