From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: Ken Brown <kbrown@cornell.edu>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Weird issue with file permissions
Date: Fri, 1 Jul 2022 22:11:32 +0000 [thread overview]
Message-ID: <DM8PR09MB7095B96979A2CE9E61A4A3DEA5BD9@DM8PR09MB7095.namprd09.prod.outlook.com> (raw)
> Cygwin does not do this on a standard installation. Is it something you've done
I did use the standard Setup and nothing else... My $HOME looks fine, too:
$ cd
$ pwd
/home/ANTON
$ getfacl .
# file: .
# owner: ANTON
# group: None
user::rwx
group::---
other::---
default:user::rwx
default:group::r-x
default:other::r-x
$ id
uid=197609(ANTON) gid=197121(None) groups=197121(None),559(Performance Log Users),545(Users),4(INTERACTIVE),66049(CONSOLE LOGON),11(Authenticated Users),15(This Organization),113(Local account),4095(CurrentSession),66048(LOCAL),262154(NTLM Authentication),401408(Medium Mandatory Level)
Whatever is on drive G: was mostly also created by Cygwin -- I was just simply moving stuff from
$HOME to there using tar (IIRC)... Initially, it was a clean and empty NTFS volume (brand new).
So it was something like:
$ mkdir /cygdrive/g/cygwin
and then for each $stuffdir I wanted moved
$ cd; tar cf - ./$stuffdir | (cd /cygdrive/g/cygwin; tar xvf -)
So, I have no idea why permissions there ended up all perplexed.
But please note that .socket gets created perfectly fine in that directory,
yet the problem occurs when that's a subdirectory, created from under Cygwin!
(and again, all's fine if mkdir for the subdir is done by Windows)
$ cd /cygdrive/g/cygwin
$ getfacl .
# file: .
# owner: ANTON
# group: None
user::rwx
group::---
group:Authenticated Users:rwx
group:SYSTEM:rwx
group:Administrators:rwx
group:Users:r-x
mask::rwx
other::---
default:user::---
default:group::---
default:group:Authenticated Users:rwx
default:group:SYSTEM:rwx
default:group:Administrators:rwx
default:group:Users:r-x
default:mask::rwx
default:other::---
next reply other threads:[~2022-07-01 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 22:11 Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2022-07-01 23:16 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2022-07-03 1:51 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-02 16:16 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-02 18:41 ` Ken Brown
2022-07-02 3:23 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-02 14:43 ` Ken Brown
2022-07-01 18:00 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-01 19:01 ` Ken Brown
2022-07-01 20:59 ` Ken Brown
2022-07-01 5:46 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-01 17:03 ` Ken Brown
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=DM8PR09MB7095B96979A2CE9E61A4A3DEA5BD9@DM8PR09MB7095.namprd09.prod.outlook.com \
--to=lavr@ncbi.nlm.nih.gov \
--cc=cygwin@cygwin.com \
--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.
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).