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 Date: Tue, 3 Dec 2002 11:10:31 -0500 From: "Pierre A. Humblet" To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.3.17 changes ls -l output Message-ID: <20021203161031.GA232171@WORLDNET> References: <20021203123649 DOT GA1788 AT tishler DOT net> <20021203151507 DOT GA326007 AT WORLDNET> <20021203154736 DOT GA1368 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021203154736.GA1368@tishler.net> User-Agent: Mutt/1.4i On Tue, Dec 03, 2002 at 10:47:36AM -0500, Jason Tishler wrote: > Pierre, > > Should the "+" be suppressed? Or, should Cygwin behave like other > Unixes (e.g., Solaris, HP-UX, etc.) that support ACLs? > The + can be suppressed by at least 3 ways: - the user should be able to remove the default entries (inheritance) when it matters (using setfacl, cacls or the Windows security gui). - ls.exe can be modified to disregard acl info. - Cygwin can be modified to not set defaults on directories. However in that case most native Windows programs would create files accessible only by the owner (or Administrators, if in group 544) and by SYSTEM. That would probably generate traffic to this list. I didn't invent the current behavior but I think it's a reasonable compromise between strict Unix behavior and being nice to users. > If the latter, then I need to submit a patch for one of the Python > regression tests. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/