From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Another chmod issue on 3.1.7, Win 10.
Date: Thu, 24 Dec 2020 18:14:18 -0500 [thread overview]
Message-ID: <54ddafd7-be92-9e9a-f675-807fb73ad29b@cornell.edu> (raw)
In-Reply-To: <62106326e8b2faf64aedb194c8fc7a3d@mail.kylheku.com>
On 12/24/2020 4:30 PM, Kaz Kylheku via Cygwin wrote:
> Initial conditions:
>
> 0:BLACKBOX:~/txr$ rm testfile
> 0:BLACKBOX:~/txr$ touch testfile
> 0:BLACKBOX:~/txr$ chmod = testfile
> 0:BLACKBOX:~/txr$ ls -l testfile
> ---------- 1 kaz kaz 0 Dec 24 13:23 testfile
>
> Now, light up all the bits, like a Christmas tree---appropriate
> for December 24:
>
> 0:BLACKBOX:~/txr$ chmod ugo+rwxs testfile
> 0:BLACKBOX:~/txr$ ls -l testfile
> -rwsrwsrwx 1 kaz kaz 0 Dec 24 13:23 testfile
>
> Well, almost all the bits: I didn't add "t", but it makes
> no difference. Anyway, so far, so good. Now, punch a hole in
> the group permissions:
>
> 0:BLACKBOX:~/txr$ ls -l testfile
> -rws---rwx+ 1 kaz kaz 0 Dec 24 13:23 testfile
>
> No idea what that + is hinting at, which indicates a problem.
No, it doesn't indicate a problem. It just means that there's an ACL involved
in determining the actual permissions. Do an internet search for "ls plus sign"
for more information.
> But the group perms did get masked out. Let's keep going to the
> main problem: repeat the second step to turn on all the bits:
>
> 0:BLACKBOX:~/txr$ chmod ugo+rwxs testfile
> 0:BLACKBOX:~/txr$ ls -l testfile
> -rws--Srwx+ 1 kaz kaz 0 Dec 24 13:23 testfile
>
> What??? The expected perms are "-rwsrwsrwx". It did not set the group read
> or write at all, and that funny + is still hanging around.
I suspect this is the same owner/group issue that I suggested in my reply to
your other message.
Ken
prev parent reply other threads:[~2020-12-24 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 21:30 Kaz Kylheku
2020-12-24 23:14 ` Ken Brown [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=54ddafd7-be92-9e9a-f675-807fb73ad29b@cornell.edu \
--to=kbrown@cornell.edu \
--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).