public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Weird issue with file permissions
Date: Fri, 1 Jul 2022 19:16:28 -0400	[thread overview]
Message-ID: <85488aed-610f-4be9-1b17-904b7de66c45@cornell.edu> (raw)
In-Reply-To: <DM8PR09MB7095B96979A2CE9E61A4A3DEA5BD9@DM8PR09MB7095.namprd09.prod.outlook.com>

On 7/1/2022 6:11 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>> 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

The "group" and "other" entries are surprising (to me), but maybe that's not 
important.  On my system I have:

$ cd

$ pwd
/home/kbrown

$ getfacl .
# file: .
# owner: kbrown
# group: None
user::rwx
group::r-x
other::r-x
default:user::rwx
default:group::r-x
default:other::r-x

> 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

At this point the permissions on /cygdrive/g/cygwin are influenced by the ACL on 
/cygdrive/g.  What I would typically do in this situation is

   getfacl ~ | setfacl -f - /cygdrive/g/cygwin

That way I'm sure I won't have any surprises with permissions when working in 
/cygdrive/g/cygwin.  Do you want to try that and see if it makes a difference?

Ken

  reply	other threads:[~2022-07-01 23:16 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]
2022-07-01 23:16 ` Ken Brown [this message]
  -- 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=85488aed-610f-4be9-1b17-904b7de66c45@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=lavr@ncbi.nlm.nih.gov \
    /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).