On 04/07/2018 08:10 PM, Anton Aylward wrote:
On 07/04/18 10:32 PM, Marc Chamberlin wrote:
Is there some weird magic about Documents folders on Windows systems? Doesn't make any sense to me... You are asking the question the wrong way. You are also not telling us some things.
First: what type of file systems was it at the windows end?
Second: how was it mounted? Hi Anton, Doug - and thanks for replying... It is an NTFS file system. Here is a typical example, from one of my autofs config files, of how I am mounting the Windows file system for a system running Win10 -
c -fstype=cifs,rw,dir_mode=0777,file_mode=0777,credentials=/etc/smb1.auth,uid=1000,gid=100,vers=2.0 ://quantumWin10/C
As I mentioned, I am using autofs to mount it. The only other bit of info that I will mention is that I mount the file system with both a timeout and the ghost option set but I would not expect that to be affecting this behavior. And yes I know that what Windows calls Permissions, under Documents properties is not the same as what Linux calls file permissions. But it was these Window's Permissions properties (along with Network and Sharing properties) that I was trying to set, to allow me access to the Documents folders, without any joy until I fooled with the Documents folder's permissions from the Linux perspective... Marc...
Old fashioned MS-dos era Windows FS doesn't have permissions and the permissions Linux sees is set by the way the FS is mounted.
See MAN(8) section FILESYSTEM-SPECIFIC MOUNT OPTIONS - Mount options for fat and also MOUNT.CIFS(8)
After reading that you should see how to mount the Windows FS so that the fiddling with permissions from the mount point down is unnecessary.
My apologies if you know this or if it is already in the way your autofs is set up. I recall learning this 'the hard way' myself a couple of decades ago.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org