HP CIFS Server 3.0a Administrator's Guide version A.02.01

Managing HP-UX File Access Permissions from Windows NT/XP/2000
UNIX File Permissions and POSIX ACLs
Chapter 3 47
For example, if an owning group named sales on the UNIX file system
has read and execute (r-x) permissions on a file, the Windows NT client
will display the permissions for group sales as:
Special Access(RXO)
UNIX Other Permission Translation in NT ACL
In UNIX, the other permission entry represents permissions for any user
or group that is not the owner, and doesn't belong to the owning group.
This entry maps to the everyone access control entry on the Windows NT
client.
NT Directory and File Permission Translations
Windows NT clients display two sets of permissions for directory entries:
directory permissions and file permissions. Directory Permissions are the
permissions for the directory itself. File Permissions are the permissions
inherited by the files and subdirectories created in the directory. Samba
translates UNIX permissions for a directory into Windows NT directory
permissions and vice versa. Windows NT file permissions are not
supported when the translation is to/from UNIX permissions.
NT file permissions, however, are supported with VxFS POSIX ACLs (as
described in the next section).
Setting UNIX Permissions from Windows NT
With one exception, reversing the UNIX to NT translations described
above will always work. You cannot, however, change the owner or
owning group by adding Special Access(DPO) or Special Access(O) to a
user or group from the client.
All NT permissions, except read, write and execute, are disregarded
when applied to files on the Samba server. These include delete (D),
change permissions (P) and take ownership (O).
The table below shows how NT access types map to UNIX permissions:
Table 3-2
NT access type UNIX Permission
Special Access(R) r--
Special Access(W) -w-
Special Access(X) --x