From: Xianwen Chen <xianwen.chen@gmail.com>
To: Thomas Wolff <towo@towo.net>, cygwin@cygwin.com
Subject: Re: can modify file on network drive, but cannot create files
Date: Wed, 11 May 2011 07:52:00 -0000 [thread overview]
Message-ID: <BANLkTi=f48W6P3Yn14Kf2BSU9V1+V0r7RA@mail.gmail.com> (raw)
In-Reply-To: <4DCA3BE4.7050405@towo.net>
Hi Thomas,
Thanks a lot!
On Wed, May 11, 2011 at 9:33 AM, Thomas Wolff <towo@towo.net> wrote:
>
> OK, in your first message you wrote you can delete but not create files
> which would have been strange.
I'm sorry that my bad command of English confused you. This is what I
wanted to say:
Cygwin can modify and delete, but not create files.
> That you can neither delete nor create files (but still existing files) is
> actually more normal (in terms of Unix-like permission).
> Just check the permissions of the directory, they should include write
> access for you. If you are the owner, you can easily change that with chmod
$ chmod +w /cygdrive/h/Temp
chmod: changing permission of 'Temp': Permission denied.
Thanks to your hint, I went on investigating:
$ ls -l /cygdrive/h/
-rwx------+ 1 myusername mkpasswd 0 May 10 22:19 Temp
I think the problem lies in the mkpasswd part of the ownership. In
UNIX, mkpasswd would be the owner group of the folder. How about in
Windows?
> +w /cygdrive/h. If you are not the owner of your own network directory, ask
> your server administrator to fix that.
Yes, I think I have to talk to him about it. ;)
Xianwen
> ------
> Thomas
>
>> On Wed, May 11, 2011 at 9:12 AM, Thomas Wolff<towo@towo.net> wrote:
>>>>
>>>> Hi Cygwiners,
>>>>
>>>> I need a hint.
>>>>
>>>> The network drive (\server\) is mounted as H:\.
>>>>
>>>> Cygwin can access files on H drive; can modify/delete files on H
>>>> drive; however, it cannot create files. The program says permission
>>>> denied.
>>>>
>>>> Do I need to write some configuration files?
>>>>
>>>> Xianwen
>>>
>>> What kind of network file system is it?
>>> Assuming a Unix-like permission system, it is quite surprising that you
>>> can
>>> delete files but not create any.
>>> Or maybe you can delete (and create) files in a subdirectory but not
>>> create
>>> (and delete) in the root directory H:\?
>>> Otherwise it might be due to some unusual ACL settings on the remote
>>> side,
>>> or maybe you have exceeded your quota (amount of allowed capacity) on the
>>> remote server? Ask the administrator.
>>> ------
>>> Thomas
>>>
>>> --
>>> Problem reports: http://cygwin.com/problems.html
>>> FAQ: http://cygwin.com/faq/
>>> Documentation: http://cygwin.com/docs.html
>>> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>>>
>>>
>>
>>
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
>
--
Backup email: v9@dr.com
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2011-05-11 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 7:01 Xianwen Chen
2011-05-11 7:12 ` Thomas Wolff
2011-05-11 7:24 ` Xianwen Chen
2011-05-11 7:23 ` Xianwen Chen
2011-05-11 7:35 ` Thomas Wolff
2011-05-11 7:52 ` Xianwen Chen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=f48W6P3Yn14Kf2BSU9V1+V0r7RA@mail.gmail.com' \
--to=xianwen.chen@gmail.com \
--cc=cygwin@cygwin.com \
--cc=towo@towo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).