From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Request to the git maintainer
Date: Tue, 11 Jul 2017 01:38:00 -0000 [thread overview]
Message-ID: <5058c577-3875-2d2f-950a-04ef54172c8d@SystematicSw.ab.ca> (raw)
In-Reply-To: <aa3bdabb-5e98-ada9-f033-15b675dee069@cs.umass.edu>
On 2017-07-10 17:17, Eliot Moss wrote:
> On 7/10/2017 6:27 PM, Kaz Kylheku wrote:
>> On 10.07.2017 14:02, Eliot Moss wrote:
>>> On 7/10/2017 4:24 PM, Achim Gratz wrote:
>
>> You can't ask every vendor of everything that you have installed
>> or "git pulled" to fix their permissions because your backup program
>> has bizarre limitations.
>
> I'm not asking "every vendor". I'm asking a limited number of
> cygwin port maintainers (and so far only one specifically).
>
> CrashPlan does not have "bizarre" limitations -- it quite
> naturally has some difficulty if a file's access does not grant
> it permission.
>
> The permissions on these files is what is bizarre. There is no
> good reason they should deny read access.
>
> Windows does not really have an equivalent of "root" that can
> access anything, so there is not really any privilege I can
> give the backup tool that is guaranteed to work in all cases.
Backup processes should run with SeBackupPrivilege.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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:[~2017-07-11 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 18:23 Eliot Moss
2017-07-10 20:24 ` Achim Gratz
2017-07-10 20:45 ` Eliot Moss
2017-07-10 21:02 ` Eliot Moss
2017-07-10 22:27 ` Kaz Kylheku
2017-07-10 23:17 ` Eliot Moss
2017-07-10 23:49 ` Erik Soderquist
2017-07-11 1:38 ` Brian Inglis [this message]
2017-07-11 2:00 ` Eliot Moss
2017-07-11 2:33 ` Brian Inglis
2017-07-11 12:34 ` Eliot Moss
2017-07-11 16:34 ` Eliot Moss
2017-07-11 20:35 ` Achim Gratz
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=5058c577-3875-2d2f-950a-04ef54172c8d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).