Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <392C0ED5.57CE0A13@vinschen.de> Date: Wed, 24 May 2000 19:18:13 +0200 From: Corinna Vinschen X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: cygdev Subject: call to writeable_directory in _unlink: Do we need it? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have a problem with the function writable_directory() On one hand it's a nice add-on to simulate UNIX permissions as near as possible but on the other hand that function disallows many functions on (writable!) samba shares if you are using ntsec. You can't unlink rename mkdir The reason is the usage of access() in writable_directory(). The access function itself takes the complete ACL of a file into account when computing the users permissions. Unfortunately, you don't have a clean mapping between NT account and UNIX account across samba if you are not using NT domain logon authentication. The result is that you typically don't have write permission on your samba directory. Nevertheless you may do nearly everything via Cygwin, except of chown, of course, but Cygwin itself disallows removing a file regardless of your _real_ permissions to do so. The same is true for mkdir() Personally I would plead for elininating the function writable_directory() since I'm sure that it's going a step too far in simulating permissions because it disallows what is allowed, actually. Objections? It's a bit urgent for me because I want to check in some other changes which clean up the permission settings in ACLs for a better co-working between Samba and Cygwin+ntsec before the next net release. Corinna