public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Erik Soderquist <ErikSoderquist@gmail.com>
To: cygwin@cygwin.com
Subject: Re: permission question
Date: Wed, 07 Dec 2016 20:12:00 -0000	[thread overview]
Message-ID: <CACoZoo3xmZbi_=NK-xj8wLx52v5OFS-TcHvYf=RROtMJYkhyDg@mail.gmail.com> (raw)
In-Reply-To: <CAGpXXZJKZFuE-yNpZJ0syjgShdkigV+kj5XudS71r0Mw+2D3Bw@mail.gmail.com>

> I really like cygwin and have used it for a decade plus.  Only in the
> last year or 18-months have I noticed significant permission issues
> that slow down my workflow.
>
> Copying these folders/files from one drive to another is a task I'd
> like to accomplish, but even more importantly I'd like to understand
> how to work with permissions in cygwin.  As it is, I'm concerned I
> will have to leave cygwin behind and I don't want to do that.

I've been a Windows and Linux admin for years, and Windows permissions
can be a pain, but can also be very granular.

What I normally do for something like this is use robocopy's "backup mode"
switch to bypass permissions on the source entirely and intentionally not
copy the permissions to the destination, then set up the permissions I want
on the destination after the copy is complete.

The "backup mode" option requires either backup operator or local admin
permissions to use.

-- Erik

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-12-07 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 15:48 Greg Freemyer
2016-12-07 16:02 ` Gluszczak, Glenn
2016-12-07 18:22 ` Greg Freemyer
2016-12-07 18:48   ` Stephen John Smoogen
2016-12-07 19:06     ` Greg Freemyer
2016-12-07 20:12       ` Erik Soderquist [this message]
2016-12-07 20:39         ` Brian Inglis
2016-12-07 22:09           ` Greg Freemyer
2016-12-07 22:28             ` Erik Soderquist
2016-12-07 23:06             ` Michel LaBarre

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='CACoZoo3xmZbi_=NK-xj8wLx52v5OFS-TcHvYf=RROtMJYkhyDg@mail.gmail.com' \
    --to=eriksoderquist@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).