From: Eli Zaretskii <eliz@gnu.org>
To: jari <jari.aalto@cante.net>
Cc: 10257@debbugs.gnu.org
Subject: bug#10257: 23.3.1 Cygwin: network drives - file is write protected (false positive)
Date: Tue, 13 Dec 2011 09:43:21 -0500 [thread overview]
Message-ID: <E1RaTZh-0006H7-3R@fencepost.gnu.org> (raw)
In-Reply-To: <20111213140042.GA22678@picasso.cante.net> (message from jari on Tue, 13 Dec 2011 16:00:42 +0200)
> Date: Tue, 13 Dec 2011 16:00:42 +0200
> From: jari <jari.aalto@cante.net>
> Cc: 10257@debbugs.gnu.org
>
> | So why don't you ask on the Cygwin list whether access() and
> | euidaccess() can be taught to give the "right" answer for files on
> | such drives. Or maybe the question is simply whether Cygwin can be
> | taught to determine the correct UID.
>
> Sure, but because The network drive is not part of Windows Domain, I'm
> afraid Cygwin has any means to determine what the correct UID or GID
> would be are as they have no correspondence on the Windows side.
??? As long as the network drive is mounted using Windows APIs (which
must be the case), the NT security features should be fully supported
for it. That includes the user and group IDs of every file. So why
does Cygwin's `stat' return 4294967295 (which AFAIU is a fancy way of
saying -1) for UID and GID of these files?
> In any case, this is a big problem in daily use; especially because
> the file system check cannot be ignored, bypassed or configured to
> "just to go ahead and write without questions".
We don't want to put some ad-hoc "solution" into Emacs just because it
is urgent for you. We want to understand the problem, and in
particular figure out whether it is an Emacs problem or a problem with
the Cygwin implementation of some library function. Only then it will
be possible to establish what is the best solution.
Ken repeatedly suggested that you ask on the Cygwin list about this.
I think this is a good idea, as people here (with the exception of
Ken) know very little about Cygwin internals.
In any case, if you don't wish to follow Ken's advice, but want to
solve this urgent problem, you have the sources, don't you?
next prev parent reply other threads:[~2011-12-13 14:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 18:23 bug#10257: 23.3.1 Cygwin: network drives - file is write protected (false positive) Jari Aalto
2011-12-09 20:33 ` Ken Brown
2011-12-10 9:58 ` jaalto
2011-12-13 12:18 ` Ken Brown
2011-12-13 14:00 ` jari
2011-12-13 14:43 ` Eli Zaretskii [this message]
2011-12-13 15:12 ` Ken Brown
2011-12-13 19:27 ` Stefan Monnier
2011-12-13 20:16 ` Ken Brown
2011-12-14 2:54 ` Stefan Monnier
2011-12-14 3:27 ` Ken Brown
2011-12-14 8:01 ` Jari Aalto
2011-12-14 8:35 ` Eli Zaretskii
2011-12-14 12:24 ` Ken Brown
2011-12-14 12:55 ` Ken Brown
2011-12-14 13:10 ` Eli Zaretskii
2011-12-14 14:19 ` Ken Brown
2011-12-14 14:47 ` jari
2011-12-14 17:30 ` Eli Zaretskii
2011-12-14 17:57 ` Ken Brown
2011-12-15 2:43 ` Ken Brown
2011-12-15 2:53 ` Ken Brown
2011-12-15 3:19 ` Ken Brown
2011-12-15 4:04 ` Eli Zaretskii
2011-12-15 14:42 ` Ken Brown
2011-12-16 19:37 ` Ken Brown
2011-12-16 19:46 ` Eli Zaretskii
2011-12-16 23:15 ` Stefan Monnier
2011-12-17 17:08 ` Ken Brown
2011-12-14 14:15 ` jari
2011-12-14 14:29 ` Ken Brown
2011-12-14 14:43 ` jari
2011-12-14 17:21 ` Eli Zaretskii
2011-12-14 17:23 ` Richard Stallman
2011-12-13 16:26 ` jari
2011-12-13 16:52 ` Ken Brown
2011-12-13 17:48 ` jari
2011-12-13 17:48 ` Eli Zaretskii
2011-12-13 18:05 ` jari
2011-12-13 18:36 ` Eli Zaretskii
2011-12-15 14:44 ` Jason Rumney
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=E1RaTZh-0006H7-3R@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=10257@debbugs.gnu.org \
--cc=jari.aalto@cante.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.