/usr/local, /var and */tmp in c:\Users\Public
Thu Nov 13 22:17:00 GMT 2014
On Nov 13 14:39, Warren Young wrote:
> On Nov 13, 2014, at 2:30 PM, Corinna Vinschen <firstname.lastname@example.org> wrote:
> > On Nov 13 14:09, Warren Young wrote:
> >> http://etr-usa.com/cygwin/ls-perms.png
> > icacls output would be more helpful than a picture.
> $ icacls ls.exe
> ls.exe MOSSYMAZE\Warren:(F)
> > It doesn't work when running under a non-admin account.
> Every other Windows setup program is playing by that same restriction.
Setup tries to install with (explicit) POSIX permissions, not with
(inherited) Windows permissions. It's not quite the same thing.
> > However, the *other* idea is that if you install with an elevated Setup,
> > your account is an admin account anyway. Ideally when you install
> > Cygwin for multiple users, you're using an account you're not using for
> > daily usage.
> Couldn’t the Cygwin non-user files be owned by SYSTEM instead of the installing user?
In a corporate model this might make sense, but for the home user? I'm
not so sure about SYSTEM, though. Administrator/Administrators sounds
right to me. SYSTEM? Hmm. As I said, at one point back in the early
1.7 days setup did something like that, but we got complaints. I don't
remember the details. But if we do something like that again, it should
be configurable. Maybe the "Just Me"/"All users" choice is sufficient
if explained sufficiently in the GUI?
Also, who's going to do that? The coding part, I mean. Lots of what's
required is already in setup, but I can't write it often enough (it's
an obsession probably): I would be very glad for developers not shy
making their hands dirty.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: not available
More information about the Cygwin