delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/11/13/15:01:32

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: Barry Kelly <bkelly DOT ie AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin Everyone group permissions and Vista "shared files" (*not* shared folders)
Date: Thu, 13 Nov 2008 20:00:32 +0000
Message-ID: <m91ph4pnikh01uitm0mb7ufuudb93j0mat@4ax.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>
In-Reply-To: <4919B55D.10606@cygwin.com>
X-Mailer: Forte Agent 4.2/32.1117
MIME-Version: 1.0
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id mADK1V55009160

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.

I have different users on my machines for various reasons, and
permissions are sometimes a problem. Concrete real-life example: on my
laptop I have a "presenter" user who has extra-large fonts, so that
folks can see code samples etc. during presentations. However, the code
samples themselves are created and edited using the normal user, and
often end up inaccessible - i.e. read-only - to the presenter user.

I have a simple utility called reset-permissions that uses chown and
chmod to recursively reset permissions to a known good state in the
directories specified as arguments. This works well enough that I don't
have to panic over file rights in the middle of a presentation.

I could write my own chown and chmod, perhaps in terms of cacls, perhaps
with custom utilities for more precise ACLs. I'd rather not have to
reimplement those utilities though.

-- Barry

-- 
http://barrkel.blogspot.com/

--
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/


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019