Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Sat, 17 Jan 2004 22:17:32 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: MS offers "Services For Unix" free of charge
Message-ID: <20040117211732.GV1885@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20040114213617 DOT GD4088 AT redhat DOT com> <ICEBIHGCEJIPLNMBNCMKKEJADBAA DOT chris AT atomice DOT net> <20040116101533 DOT GK1885 AT cygbert DOT vinschen DOT de> <40083A57 DOT 30200 AT attglobal DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40083A57.30200@attglobal.net>
User-Agent: Mutt/1.4.1i

On Jan 16 11:24, Doug VanLeuven wrote:
> Corinna Vinschen wrote:
> >Even though it allows mapping between UNIX user names (from the evil
> >"other" side) and Windows user names, it doesn't map the POSIX permission
> >bits into NTFS like permissions.  If you look into the file property box,
> >you'll see no "Security" tab.  The file access from Windows is a bit like
> >access to files on FAT partitions.  The permissions are statically set in
> >an administration MMC snap-in.
> >[...]
> I'm not a particular fan of MS NFS client (slow), and I don't know what 
> version you worked with, but V3.0 client certainly can set 
> user/group/other permissions, in other words, there is a security tab.

This is a special tab which is unfortunately not a mapping to NTFS
permissions in a way which is transparent to applications.  IOW,
you won't be able to use Cygwin's chmod or chown on NFS shares for that
reason.  Tests show that e. g. the system call GetFileSecurity() just
returns with Windows error 2 (No such file) on files on an NFS share.
The GetVolumeInformation() call returns with the below information:

    Max Filenamelength : 255
    Filesystemname     : NFS
    Flags:
      FILE_CASE_SENSITIVE_SEARCH  : FALSE
      FILE_CASE_PRESERVED_NAMES   : TRUE
      FILE_UNICODE_ON_DISK        : FALSE
      FILE_PERSISTENT_ACLS        : FALSE
      FILE_FILE_COMPRESSION       : FALSE
      FILE_VOLUME_QUOTAS          : FALSE
      FILE_SUPPORTS_SPARSE_FILES  : FALSE
      FILE_SUPPORTS_REPARSE_POINTS: FALSE
      FILE_SUPPORTS_REMOTE_STORAGE: FALSE
      FILE_VOLUME_IS_COMPRESSED   : FALSE
      FILE_SUPPORTS_OBJECT_IDS    : FALSE
      FILE_SUPPORTS_ENCRYPTION    : FALSE
      FILE_NAMED_STREAMS          : FALSE

As you can see, accessing NFS shares using the SFU 3.5 NFS client 
doesn't support persistent ACLs, which would represent the transparent
interface I was talking about.  It isn't even mounted as case sensitive
file system!

Probably there is an ABI somewhere but it would require special
programming considerations.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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