public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: file permission problem
Date: Sat, 16 Apr 2016 20:38:00 -0000	[thread overview]
Message-ID: <18b4b0d7-e277-9568-642e-7807c8140b2e@gmail.com> (raw)
In-Reply-To: <5711925B.7070506@ca.rr.com>

On 16/04/2016 03:16, Barry Gold wrote:
> I updated my cygwin to the latest 32-bit version (I hope), and I'm
> having a problem with file permissions. Newly created files and
> directories lack write permission even for the owner.
>
> Here's some relevant stuff from my Cygwin shell window:
>
> -----------------
> ~ % umask
> 0022
> ~ % touch x
> ~ % ll x
> -rw-rw-r--+ 1 barry None 0 Apr 15 18:13 x
> ~ % ll .
> drwxrwx---+ 1 barry None 0 Apr 15 18:13 ./
> ~ % cd bin
> ~/bin % ll .
> drwxr-xr-x+ 1 barry None 0 Apr 15 18:12 ./
> ~/bin % touch x
> ~/bin % ll x
> -r--r--r--+ 1 barry None 0 Apr 15 18:13 x
> ~/bin %
> -----------------
>
> If I create a file in my home directory, the file permissions come out
> correct. But if I create a file in my bin directory, the file
> permissions are wrong -- write permission is missing, even for the owner
> (me).
>
> This is x86 cygwin on Windows 7 Home Premium Service Pack 1
>

check ACL permissions of the directory

  icacls bin

--
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-16 20:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-16  1:16 Barry Gold
2016-04-16 20:38 ` Marco Atzeri [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-28  0:57 Win Tong
2007-11-28  1:07 ` Larry Hall (Cygwin)
2004-09-24 16:26 File " Hughes, Bill
2004-09-24  8:35 jackylam
2004-09-24  7:21 jackylam
2004-09-24  9:31 ` Brian Dessent
2004-09-24  9:31   ` Corinna Vinschen
2004-09-24  9:47     ` Brian Dessent
2004-09-24 12:42       ` Corinna Vinschen
2004-09-24 14:51         ` Andrew DeFaria
2004-09-24 14:58           ` Christopher Faylor
2004-09-24 15:08             ` Andrew DeFaria
2004-09-24 15:19               ` Corinna Vinschen
2004-09-24 16:41                 ` Andrew DeFaria
2004-09-24 14:59           ` Doctor Bill
2004-09-24 15:09             ` Corinna Vinschen
2004-09-24  5:19 jackylam
2004-09-24  5:22 ` Peter Rehley
2004-09-24  2:53 jackylam
     [not found] ` <6334E09627481B4AA5C8DE1E69E19D3B013BA6EB@SSLEXCHANGE.solom onsystech.com>
2004-09-24  3:31   ` Larry Hall
2004-09-24 13:20     ` Doctor Bill
2004-09-24 13:37       ` Doctor Bill

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=18b4b0d7-e277-9568-642e-7807c8140b2e@gmail.com \
    --to=marco.atzeri@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).