Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <3.0.5.32.20030926212951.00822b50@incoming.verizon.net> X-Sender: vze1u1tg AT incoming DOT verizon DOT net (Unverified) Date: Fri, 26 Sep 2003 21:29:51 -0400 To: cygwin AT cygwin DOT com, Marco Mason From: "Pierre A. Humblet" Subject: Re: Installed, Admin can run, other account can't... In-Reply-To: References: <3F745893 DOT 42F40E25 AT npc DOT net> <3F7360C6 DOT 53FB260C AT npc DOT net> <3F745893 DOT 42F40E25 AT npc DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:31 AM 9/26/2003 -0400, Igor Pechtchanski wrote: > >The "real" fix would be to make setup create the directories with the >right permissions from the start. I'm not sure this is possible. >Perhaps people with more knowledge of ACLs (Pierre, Corinna, CGF?) will >chime in and offer their opinions... Sure, but what are the right permissions? Some people objet to giving access to Everybody. The group name and whether the group should have write access are matters of local preference. So setup uses the default inheritable acl of the directory under which cygwin is installed. It works just fine in most cases. I don't know why in this case group Users got no rights. This is not a typical factory default, it was most probably set that way for some local reason. Perhaps the exit message of setup should be to remind the installer to verify the permissions (PTC). Or perhaps that's another test that could be added into /etc/profile, nagging the user "are you sure this is really what you want". Pierre -- 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/