From: jari <jari.aalto@cante.net>
To: Ken Brown <kbrown@cornell.edu>
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 19:48:17 +0200 [thread overview]
Message-ID: <20111213174817.GC22678@picasso.cante.net> (raw)
In-Reply-To: <4EE782DB.3030600@cornell.edu>
On 2011-12-13 11:52, Ken Brown wrote:
| On 12/13/2011 11:26 AM, jari wrote:
| >Response from Cygwin list:
| >
| > > $ ls -la /cygdrive/z/tmp/test-epackage.el
| > > -rwxr--r-- 1 ???????? ???????? 437 Dec 9 20:02 /cygdrive/z/tmp/test-epackage.el
| >
| > It's not a bug.
| >
| > If you use winbind and the user accounts are correctly mapped to
| > Windows accounts, then you would see the Cygwin UIDs/GIDs
| > correspoding to the SID of the AD user account.
| >
| > If you don't do that, there's only an invisible mapping from the
| > Windows SID to the Unix uid/gid. The actual UNIX account has not
| > the same mapping back to the Windows SID. Instead, the SID
| > returned from Samba to Windows is a fake SID S-1-22-1-UnixUID or
| > S-1-22-2-UnixGID. (..)
| >
| >The rest goes into details for setting 1:1 UID, GID mapping.
|
| You omitted the part of the response that says, "The easiest way to
| workaround this issue is to mount the share with the noacl mount
| option".
| Does this fail to work for some reason?
That would create a new "Cygwin mount". Different path altogether than
what is already in use; mapped by the Windows.
In Windows: Z:\
In Cygwin : /cygdrive/z
All paths would change if I would Cygwin mount(1) "//server/login
/mnt/login ..."
/mnt/login <!=!> /cygdrive/z
That would create problems all over the place that now assume certain
locations. Not to mention losing ability to copy/paste paths from
Windows File Exporer to Cygwin[*]
Jari
[*] Cygwin accepts drive letter syntax in single quotes: 'z:\'
See also cygoath(1).
next prev parent reply other threads:[~2011-12-13 17:48 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111213174817.GC22678@picasso.cante.net \
--to=jari.aalto@cante.net \
--cc=10257@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).