From: Greg Freemyer <greg.freemyer@gmail.com>
To: cygwin@cygwin.com
Subject: Re: permission question
Date: Wed, 07 Dec 2016 19:06:00 -0000 [thread overview]
Message-ID: <CAGpXXZJKZFuE-yNpZJ0syjgShdkigV+kj5XudS71r0Mw+2D3Bw@mail.gmail.com> (raw)
In-Reply-To: <CANnLRdgjY5oQF1hLE75tg_b4ut881PFp+=uWB6jtN1-ya7sf2w@mail.gmail.com>
On Wed, Dec 7, 2016 at 1:48 PM, Stephen John Smoogen <smooge@gmail.com> wrote:
>> I'm tempted to just do a "chmod 755 -R .", but I've just had too many
>> windows permission issues in the last year to start trying things
>> without guidance.
>
> That would probably make things worse. I believe that Windows
> permissions are like attribs in Linux (which moves it into witchcraft
> and sorcery). For dealing with this sort of issue I would look at
> using the xcopy that Glenn from dell mentioned.
>
>> Greg
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.
Greg
--
Greg Freemyer
--
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
next prev parent reply other threads:[~2016-12-07 19:06 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 [this message]
2016-12-07 20:12 ` Erik Soderquist
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=CAGpXXZJKZFuE-yNpZJ0syjgShdkigV+kj5XudS71r0Mw+2D3Bw@mail.gmail.com \
--to=greg.freemyer@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).