Hi,

It seems that by default a Windows share mounted at /mnt/Windows/ will be owned by root and have 755 permissions set on all files.

I usually do a chown or chmod to allow my user to have write access to these files. Does that affect the Windows files in any way? It takes quite some time to complete the chown/chmod when there's a lot of data.

Where is the Linux permission data kept for the Windows share? On the Linux computer where I set the permissions?

I just want to get a better understanding how this works.

Thanks

For a samba share, use the "uid" and "gid" options to change the ownership of files. This is necessary if the server doesn't support the cifs extensions.

Permissions are determined when you mount as well with the file_mode and dir_mode options.

See the mount manpage. Also the mount.cifs manpage.

0 members found this post helpful.

I'm not trying to control the Windows permissions from Linux; I'm treating them as two separate systems. I just want to know what's happening when I'm "chowning"/"chmodding" Windows files from Linux. All seems to work OK.

Do you have AD authentication / LDAP setup on your Linux system and if so are you giving permissions to an identified user on the Windows box or are you giving permissions to a user defined in /etc/passwd.

0 members found this post helpful.

Nope, no integration at all; two separate systems on the same network.

Since there is no pass through authentication, and you are assigning permissions to a user from /etc/passwd the windows system should assign default permissions to the file / folder based on the permissions of the upper level folder(s) so if SYSTEM, Administrator, and UserX have permissions to the upper level folder and they are set to inherit to sub-folders that new file should receive those permissions. If you had something like Likewise or another AD integration package you could assign permissions to DOMAIN/User on the Linux side since there would be UID/GID mapping and that user would exist on the Windows side and retain those permissions (*should). But since you don't you should only see inherited permissions to the new files.

0 members found this post helpful.