implemented attribute mapping and chmod. file attributes are mapped in

the same manner as smbd. See the README for a full explanation.
(This used to be commit 0a5dcddd3fa23081d7cd214acc32b8046125a74e)

1 files changed, 19 insertions, 1 deletions

diff --git a/source3/smbwrapper/README b/source3/smbwrapper/README
index e9a52fb247..9f18c33036 100644
--- a/source3/smbwrapper/README
+++ b/source3/smbwrapper/README
@@ -30,7 +30,8 @@ happens. If you set SMBW_WORKGROUP to your workgroup or have workgroup
 set in yoru smb.conf then listing /smb/ should list all SMB servers in
 your workgroup.
 
-Environment variables
+
+ENVIRONMENT VARIABLES
 ---------------------
 
 SMBW_USER
@@ -58,6 +59,23 @@ SMBW_WORKGROUP
  /smb/ directory). It defaults to the one set in smb.conf.
 
 
+ATTRIBUTE MAPPING
+-----------------
+
+smbwrapper does an inverse attribute maping to what Samba does. This
+means that the archive bit appears as the user execute bit, the system
+bit appears as the group execute bit and the hidden bit appears as the
+other execute bit. You can control these with chmod. The mapping can
+be enabled an disabled using the normal smb.conf controls (ie. "map
+archive", "map system" and "map hidden").
+
+Read-only files appear as non-writeable by everyone. Writeable files
+appear as writeable by the current user.
+
+
+WHAT WORKS
+----------
+
 Things that I have tried and do seem to work include:
 
   emacs, tar, ls, cmp, cp, rsync, du, cat, rm, mv, less, more, wc, head,