X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 14 Nov 2008 10:46:57 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin Everyone group permissions and Vista "shared files" (*not* shared folders) Message-ID: <20081114094657.GE19442@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5e4cc4153gf115hcpi4ilk2s787klg6sra AT 4ax DOT com> <20080929165252 DOT GC11053 AT calimero DOT vinschen DOT de> <20080930163346 DOT GK11053 AT calimero DOT vinschen DOT de> <20415300 DOT post AT talk DOT nabble DOT com> <20081110115230 DOT GA2884 AT calimero DOT vinschen DOT de> <7j5ih4pea29aj7pnmn186b8uitoeboetkb AT 4ax DOT com> <4919B55D DOT 10606 AT cygwin DOT com> <491C8DF5 DOT 2070301 AT cygwin DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <491C8DF5.2070301@cygwin.com> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Nov 13 15:28, Larry Hall (Cygwin) wrote: > Barry Kelly wrote: >> Larry Hall (Cygwin) wrote: >>> Barry Kelly wrote: >>>> Corinna Vinschen wrote: >>>> >>>> I, for one, use Cygwin not primarily as a POSIX emulation layer, but as >>>> my main Windows user interface. IMHO in this situation, being posixly >>>> correct is a handicap that Cygwin could do without, at the user's >>>> choice. >>> So what about the "nontsec" option doesn't address your need then? >> It disables NT ACL manipulation via chmod, chown and chgrp. > > Understood. But this is allowed under SUSV3. Cygwin has getfacl/setfacl Erm... I'm not sure what SUSv3 has to do with that. I really don't like the idea to make excemptions just for a small part of the harddisk which gets mistreated by Microsoft. Don't do Cygwin stuff in your Windows home dir, create a Cygwin specific home dir instead. If that's not feasible, switch off ntsec and you get standard Windows permissions. If the standard Windows permissions are not as you need them, don't rely on Cygwin's chown/chmod. rather change the inheritence settings of the parent directory according to your needs. Then you get the required permissions right from the start. Nothing against using chown/chmod in some border cases, Berry, but in your situation they are just a workaround for bad permission settings. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/