Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <389573C9.9B48F178@vinschen.de> Date: Mon, 31 Jan 2000 12:36:41 +0100 From: Corinna Vinschen X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: de,en MIME-Version: 1.0 To: Kevin Wright CC: Cygwin Subject: Re: B20.1: File permissions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Kevin Wright wrote: > [...] > Anyway I was informed if I downloaded a later snapshot, and set CYGWIN=ntsec > then this would solve my problem. > > Sure enough the ls -l and test -w inconsistency disappeared under these > conditions. Now I have the marvellous state of affairs where ls -l says a > file is writable and attrib says the file is read only. It's a bug in the latest snapshots. When ntsec is set, only the security attributes are taken into account but the old DOS file attributes are ignored. The problem is that NTFS has both attribute types which may differ. You, as the owner of the file, have security attributes that allow writing while the old DOS type file attribute has the read-only bit set. This is sick, IMHO, but you are right: It should be handled. I will fix it in one of the next snapshots. Nevertheless I would like to suggest _not_ using the old DOS attributes on NTFS. When using ntsec, you have nearly full access to the NTFS security attributes. The latest snapshots include tools named 'getfacl' and 'setfacl' to additionally get/set attributes that are not related to user/group/other. > Would purchasing Cygwin 1.0 help to solve my problems ? No. Corinna -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com