public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: vinay Hegde <vinay.dhegde@gmail.com>
To: cygwin@cygwin.com
Subject: Problem with cp.exe (in Cygwin 3.6 64 bit): permission preserve
Date: Tue, 13 Oct 2020 18:30:25 +0530	[thread overview]
Message-ID: <CAB848Xs3DrqFS73esdQVJUnUgiPFs_FznYOmjBiR35NW-CCeGg@mail.gmail.com> (raw)

Hello Cygwin Team,
We are upgrading Cygwin from 1.7.31 32 bit to 3.6 64 bit.

With the earlier version, 'cp -fp' command used to work without any
error. Now, we get an error like, 'cp: preserving permissions for
<file_name> not supported.

Here is my understanding about ACLs & File permission in Cygwin:
Windows ACLs will be translated/mapped to POSIX like in Cygwin (This
includes user, group & permissions). Cygwin uses some logic to
implement this (using Solaris API, using SFU, ACEs accumulated for the
'access allowed' etc.)

I understand that, POSIX style is introduced from version 1.7.34.

If my understanding is correct, prior to version 1.7.34, it was using
UNIX like permission(not POSIX). In both cases (UNIX/POSIX),
permission preserve has no real meaning.
To disable this translation(to UNIX/POSIX), we had to set 'nontsec'
CYGWIN variable in old Cygwin and we have to set 'noacl' in
/etc/fastab for the new Cygwin

But my question here is,
'cp -fp' was working with Cygwin 1.7.31. Why it is NOT working now
with Cygwin 3.6?
Note: We were NOT using 'nontsec' before & now, it's equivalent
'noacl' is also not used.
If I use 'noacl' in the cygwin, 'cp -fp' doesn't complain.

Regards
Vinay Hegde

                 reply	other threads:[~2020-10-13 13:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAB848Xs3DrqFS73esdQVJUnUgiPFs_FznYOmjBiR35NW-CCeGg@mail.gmail.com \
    --to=vinay.dhegde@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).