This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Question: Desired owner/group when running setup-1.7.exe


On Apr 20 14:26, Julio Costa wrote:
> On Mon, Apr 20, 2009 at 11:07, Corinna Vinschen wrote:
> > On Apr 19 10:27, Julio Costa wrote:
> >> >> [X ] If the current user is an administrative user, make "Administrators"
> >> >> the owner of the files:
> >> >>
> >> >> owner: Administrators.
> >> >> group: The primary group of the account running setup.
> >> >>
> >> >> Comment: ____________________________________________________________
> >> >>
> >> >>[...]
> >> I'm also more inclined to the 3rd option, although I've not taken that
> >> decision easily, because user foo would not see his/her files as foo's
> >> but as Admins's (actually root). But seems to be the more "compatible"
> >> solution. The least harm law...
> >
> > WHy do you think that? ?Setup.exe has nothing to do with the Cygwin DLL
> > as far as file ownership is concerned. ?The files installed from the
> > distro will be owned by Administrators, the files created within Cygwin will
> > be owned by the user itself.
> 
> I know that setup.exe is independent of cygwin.dll but - now I'm
> confused - are you saying that ONLY files installed by setup.exe will
> follow this new ownership rule, but subsequent executions / copying /
> file creations, etc, *inside* Cygwin environments will still use
> Admin:None or whatever for ownership?

Sure.  If you don't like the default group, change it in /etc/passwd(*).
If you don't like the owner, use chown.

> Are you saying that the proposed changes will be only at the
> *packaging* level, forced to have owner uid to that of Admins?

Yes.

> In that case, how will you enforce ownership on pos-instalation scripts?

That's the job of the script.

> That doesn't make much sense... and it's not even coherent behavior.
> And surely will break things in the long run.

I don't think so.  And I dislike the idea extremly that files created by
a user foo are owned by the admins group, just because the user is a
member of the admins group.  That's not the default anymore in Windows
since at least XP, if not Windows 2000.  Also, many postinstall files
are user files.  You wouldn't want the files in your own homedir being
owned by the admins group.

Other than that, Cygwin is still a POSIX environment, not some native
Windows tool.  Along these lines, the second suggestion (owner: user,
group: admins) might be more correct.


Corinna

(*) I take it for granted that you read the User's Guide.

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]