From: "Kaz Kylheku (Cygwin)" <743-406-3965@kylheku.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: cygwin@cygwin.com
Subject: Re: chmod issue on 3.1.7.
Date: Fri, 25 Dec 2020 01:15:22 -0800 [thread overview]
Message-ID: <6640bdc9f4c413faa3b16f933bf8d97b@mail.kylheku.com> (raw)
On 2020-12-24 14:56, Ken Brown via Cygwin wrote:
> Could the problem be that the owner and group are the same? You can
> do that on unix, but I'm not sure the Windows security model allows
> it. For example, what happens when you remove permissions of the
> owner kaz while retaining the permissions of the group kaz? As far as
> Windows is concerned, you're talking about BLACKBOX\kaz in both cases,
> I think.
I have no idea where that came from. All files in the Cygwin
installation
(/bin, /usr/bin, /lib, ...) are owned by kaz:kaz. Numerically,
197613:197613. The UID and GID are the same number.
I don't see a passwd file any more in current Cygwin, but getpwent
works:
4$ txr
This is the TXR Lisp interactive listener of TXR 243.
Quit with :quit or Ctrl-D on an empty line. Ctrl-X ? for cheatsheet.
1> (getpwent)
#S(passwd name "kaz" passwd "*" uid 197613 gid 197613 gecos
"U-BLACKBOX\\kaz,S-1-5-21-3442361740-4082249206-548862920-1005"
dir "/home/kaz" shell "/bin/bash")
2> (getpwent)
#S(passwd name "SYSTEM" passwd "*" uid 18 gid 18 gecos "U-NT
AUTHORITY\\SYSTEM,S-1-5-18"
dir "/home/SYSTEM" shell "/bin/bash")
I have no clue where this configuration came from. Is there some
prompting
for these names when a new installation is made?
If nobody else has this problem, I must have done something wrong.
next reply other threads:[~2020-12-25 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 9:15 Kaz Kylheku (Cygwin) [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-10 16:32 Kaz Kylheku (Cygwin)
2020-10-10 19:41 ` Ken Brown
2020-10-10 21:51 ` Brian Inglis
2020-10-11 16:13 ` Kaz Kylheku (Cygwin)
2020-12-24 21:13 ` Kaz Kylheku (Cygwin)
2020-12-24 22:56 ` Ken Brown
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=6640bdc9f4c413faa3b16f933bf8d97b@mail.kylheku.com \
--to=743-406-3965@kylheku.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).