public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hughes, Bill" <Bill.Hughes@cox.co.uk>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: man 1.5j - can't find cat, tbl, nroff, less
Date: Wed, 24 Sep 2003 10:58:00 -0000	[thread overview]
Message-ID: <4989AFD7505BD611961B0002A5DA3E740382BE2C@NNHML2> (raw)

Sent: 23 September 2003 17:32 From: Kevin Van Workum
> I had the same problem this morning after changing the share permission on
> my C-drive from Everyone, to Administrator and Kevin. Once I added
> Administrators (note the "s"), the problem was fixed. I guess /bin/cat,
> etc were owned by Administrators and not Administrator. Whatever.

Hmmm, adding 'administrators' did fix the problem.
As which user (uid) does cygwin run?
The owner of the files in /bin is the 'administrators' group, and the owning
group is 'Domain Users'.
I presume cygwin is checking NT file system permissions for the owner and if
this is denied it doesn't check to see if the current userid is a member of
that owner (which is a group in this case), it's a little odd as if the
owner does have NT file permissions to the files it does appear to perform
that check.
Rather than add administrators to the root file permissions for the drive
(D: in my case), is there a major problem with changing the owner from the
administrators group to the 'system' id and adding execute permission for
the domain users group? i.e. from 500 to 510.
I suppose this comes back to 'as which user does cygwin run?'.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2003-09-24  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 10:58 Hughes, Bill [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-23 14:43 Hughes, Bill
2003-09-23 17:10 ` Kevin Van Workum

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=4989AFD7505BD611961B0002A5DA3E740382BE2C@NNHML2 \
    --to=bill.hughes@cox.co.uk \
    --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).