public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dave Caswell <dave.caswell@gmail.com>
To: Tatsuro MATSUOKA <matsuoka@nuce.nagoya-u.ac.jp>
Cc: cygwin@cygwin.com
Subject: Re: Permission Problems
Date: Tue, 26 Apr 2016 01:28:00 -0000	[thread overview]
Message-ID: <CAG2dRtFw0X69dvz4dc4Jehitng=WEpdQF7SwGcGuvz3im7Ts1A@mail.gmail.com> (raw)
In-Reply-To: <618133.99640.qm@web101102.mail.kks.yahoo.co.jp>

On Mon, Apr 25, 2016 at 4:30 AM, Tatsuro MATSUOKA
<tmacchant2@yahoo.co.jp> wrote:
>> From: Dave Caswell
>> To: cygwin
>            > Cc:
>> Date: 2016/4/25, Mon 09:29
>> Subject: Permission Problems
>>
>>T his is a followup to: https://cygwin.com/ml/cygwin/2016-03/msg00345.html
>>
>> To recap, making three nested directories  on a non-C drive produces a
>> third level which is unusable.
>>
>> davec@MERCURYWIN ~/python
>> $ rm -rf g1
>> davec@MERCURYWIN ~/python
>> $ mkdir g1 g1/g2 g1/g2/g3
>> davec@MERCURYWIN ~/python
>> $ ls -la g1 g1/g2 g1/g2/g3
>> g1:
>> total 12
>> drwxrwxr-x+ 1 davec None 0 Mar 16 20:23 ./
>> drwxrwx---+ 1 davec Users 0 Mar 16 20:23 ../
>> drwsrwsr-t+ 1 davec None 0 Mar 16 20:23 g2/
>> g1/g2:
>> total 0
>> drwsrwsr-t+ 1 davec None 0 Mar 16 20:23 ./
>> drwxrwxr-x+ 1 davec None 0 Mar 16 20:23 ../
>> d--Srws--T+ 1 davec None 0 Mar 16 20:23 g3/
>> ls: cannot open directory 'g1/g2/g3': Permission denied
>>
>> The problem went away with Cygwin 2.5.0-0.7 but is back with 2.5.1-1,
>> and goes away when I downgrade back to 2.5.0-1
>>
>> More info:  I tested on a couple of external drives and things worked
>> properly there.   Can I have screwed up the permissions on my D drive
>> so that cygwin gets confused but Windows still works?
>>
>> thanks
>>
> Perhaps workaround is to use the beloe
> $ cygstart --action=runas (cygwin command)
>
> In your case,
> $ cygstart --action=runas ls -la g1 g1/g2 g1/g2/g3
> Tatsuro

The problem is the creation of a directory (or file) with a mangled
ACL..  at least windows isn't capable of dealing with the directory
either.

--
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-04-26  1:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25  1:03 Dave Caswell
2016-04-25 10:30 ` Marco Atzeri
2016-04-26  7:53   ` Dave Caswell
2016-04-25 12:43 ` Tatsuro MATSUOKA
2016-04-26  1:28   ` Dave Caswell [this message]

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='CAG2dRtFw0X69dvz4dc4Jehitng=WEpdQF7SwGcGuvz3im7Ts1A@mail.gmail.com' \
    --to=dave.caswell@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=matsuoka@nuce.nagoya-u.ac.jp \
    /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).