[opensuse] File/folder permissions that does not make sense to me!
I wonder if some kind guru could explain this logic to me or direct me to an appropriate users group... I have a mixed SOHO network in my home with both Linux and Windoz systems running on it. I use autofs to automount Windows folders on my Linux systems and for the most part I don't have any issues. But one thing that has been perplexing me is why I could not copy files from say my Linux laptop to my Windows system at the C:/Users/marc/Documents folder. (I automount C: using autofs under /mnt/samba/windowscomputername/C so I can have access to the entire drive from my laptop) What really perplexed me was that I could copy files to any subfolder under C:/Users/marc/Documents such as to C:/Users/marc/Documents/tmp/newfile. My instincts told me there had to be some sort of permission problem that I had to resolve on the Windows system. So I tried everything I could think of to relax the permissions so that anyone and everyone could access the Documents folder, but to no joy. It finally occurred to me to try and take a look at it from the Linux side, so using Dolphin I examined the permissions of the Documents folder and sure enough Dolphin was reporting that I only had read permissions on the Documents folder. So on a lark I decided to try and change the permissions via Dolphin (chmod also behaved the same way) to give me read/write permissions and I will be damned if that didn't work! But I will be twitched if I can understand why in the world that worked and why I have to give myself permission to write to the Documents folder on a Windows system, from/on the Linux system side also! Shouldn't file permissions and access be strictly governed by the system that owns the files and folders? Why does a Linux system user have to give himself/herself permissions in order to write to files on a different system? This is effectively saying that in order to write to a file system on another computer I have to give myself permission to do so on BOTH systems! In other words, it wasn't Windows that was blocking me from writing to the Windows file system from my Linux laptop, it apparently was Linux itself! Is there some weird magic about Documents folders on Windows systems? Doesn't make any sense to me... Just to be certain, I took a look at the folder permissions, under Windows, both before and after making the permission change on the Linux system, and I could not see any changes so this appears to be strictly a Linux side permissions issue... Marc.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/07/2018 10:32 PM, Marc Chamberlin wrote:
I wonder if some kind guru could explain this logic to me or direct me to an appropriate users group...
I have a mixed SOHO network in my home with both Linux and Windoz systems running on it. I use autofs to automount Windows folders on my Linux systems and for the most part I don't have any issues. But one thing that has been perplexing me is why I could not copy files from say my Linux laptop to my Windows system at the C:/Users/marc/Documents folder. (I automount C: using autofs under /mnt/samba/windowscomputername/C so I can have access to the entire drive from my laptop) What really perplexed me was that I could copy files to any subfolder under C:/Users/marc/Documents such as to C:/Users/marc/Documents/tmp/newfile. My instincts told me there had to be some sort of permission problem that I had to resolve on the Windows system. So I tried everything I could think of to relax the permissions so that anyone and everyone could access the Documents folder, but to no joy.
It finally occurred to me to try and take a look at it from the Linux side, so using Dolphin I examined the permissions of the Documents folder and sure enough Dolphin was reporting that I only had read permissions on the Documents folder. So on a lark I decided to try and change the permissions via Dolphin (chmod also behaved the same way) to give me read/write permissions and I will be damned if that didn't work! But I will be twitched if I can understand why in the world that worked and why I have to give myself permission to write to the Documents folder on a Windows system, from/on the Linux system side also! Shouldn't file permissions and access be strictly governed by the system that owns the files and folders? Why does a Linux system user have to give himself/herself permissions in order to write to files on a different system? This is effectively saying that in order to write to a file system on another computer I have to give myself permission to do so on BOTH systems! In other words, it wasn't Windows that was blocking me from writing to the Windows file system from my Linux laptop, it apparently was Linux itself! Is there some weird magic about Documents folders on Windows systems? Doesn't make any sense to me...
Just to be certain, I took a look at the folder permissions, under Windows, both before and after making the permission change on the Linux system, and I could not see any changes so this appears to be strictly a Linux side permissions issue...
Marc....
This confuses me also. I an running a similar Linux system--PCLOS--and I have been able to read and write and copy from and to Windows 10 on the same or a different drive on the same computer without problems, using Dolphin, but I may have been in root mode--I don't remember. However, I do know that there are no permission bits in Windows! Windows does not understand permissions. I can also move files from the Windows file system to Linux and vice-versa on different computers via USB flash drive. (I'm too stupid to do it over the network.) --doug Comments welcome! --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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? 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. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 2018-04-08 05:46, Marc Chamberlin wrote:
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
That's not the full fstab line. It would be better if you posted the actual output of the "mount" command, the line pertaining to this mount point. But I can see from the above that maybe only user 1000 will have write access. And no, you can not change permissions with chmod on an ntfs disk. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 04/08/2018 03:10 AM, Carlos E. R. wrote:
That's not the full fstab line. It would be better if you posted the actual output of the "mount" command, the line pertaining to this mount point.
Hi Carlos - OK here is what the "mount" command shows. It actually shows the mount point twice because I do a bind mount of the root "/" to "/slash" -
mount | grep quantum /srv/autofs/auto.quantum.Win10 on /mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect) /srv/autofs/auto.quantum.Win10 on /slash/mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect)
(sorry these lines get broken up when doing a copy paste....) As I mentioned I don't mount these directly in fstab, but I use autofs instead. So I will give you full disclosure of the contents of the autofs configuration files so that you can fully understand how I am mounting the Windows file system. In the file /etc/auto.master the relevant line is -
/mnt/samba/Win10/quantum /srv/autofs/auto.quantum.Win10 --timeout=5 --ghost
That points to the actual mount configuration file (in a separate partition /srv so I can reuse it whenever I upgrade openSuSE) and the contents of /srv/autofs/auto.quantum.Win10 is what I previously showed you -
# # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage c -fstype=cifs,rw,dir_mode=0777,file_mode=0777,credentials=/etc/smb1.auth,uid=1000,gid=100,vers=2.0 ://quantumWin10/C
But I can see from the above that maybe only user 1000 will have write access.
And no, you can not change permissions with chmod on an ntfs disk.
From the responses I am getting here, my guess is that no one else has seen this, and yes for the most part accessing mounted file systems works for me as well. But this problem has showed up for my on all my Windows mounted file systems for the Documents folder so I don't know what to make of it. I can work around it, now that I know how, but it just seems very wrong that Linux is working with some sort of perceived
And I agree with you, it doesn't make sense to me that doing a chmod on an ntfs disk would affect anything. But that is exactly what happened and hence my inquiry. I had tried everything I could think of on the Windows system (quantumWin10) directly, to open up C:/Users/marc/Documents to allow me to copy a file from my OpenSuSE laptop into that Documents directory, but nothing worked. What was even more surprising was that I could create a sub-directory - C:/Users/marc/Documents/tmp and was able to copy files there. I have been doing this as a workaround, hoping that someday this problem would get fixed in an update, but it never has. This problem goes way back and I have never bothered reporting it cause I can work around it, although it is a PITA. Anywise, I decided to try and tackle this problem again and this time I discovered that by changing the apparent permissions on my Linux laptop, on /mnt/samba/Win10/quantum/C/Users/marc/Documents from -r--r--r-- to -rw-r--r--, I was then able to copy files into the Documents folder from my OpenSuSE laptop! Totally surprised me because I did that on a whim without expecting it to work... What this is saying to me is the Linux has a perspective of what the permissions are on mounted Windows NTFS file systems that is independent of actual permissions as understood by the Windows system. And that this *perceived* perspective must be changed also since it affects one's ability to access mounted Windows file systems. If I am right, then IMHO this is an extremely bad model, since it is totally confusing and NOT intuitively obvious on how to set permissions so as to make a mounted file system usable. permissions that are not related to the actual permissions of a Windows folder, and that I have to set the permissions on both systems in order to write to the Documents folder. Thoughts? Marc.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/04/2018 16:21, Marc Chamberlin wrote:
I can work around it, now that I know how, but it just seems very wrong that Linux is working with some sort of perceived permissions that are not related to the actual permissions of a Windows folder, and that I have to set the permissions on both systems in order to write to the Documents folder.
Maybe the documents folder isn't the documents folder? Weird thing to say, I know, but I the name of the folder in Windows seems to change depending on the route used to access it. I know you said you changed permissions at the linux level, but Windows does with Documents / My Documents is weird, and maybe there's some daft interaction going on there ... Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Wols Lists <antlists@youngman.org.uk> [04-08-18 13:12]:
On 08/04/2018 16:21, Marc Chamberlin wrote:
I can work around it, now that I know how, but it just seems very wrong that Linux is working with some sort of perceived permissions that are not related to the actual permissions of a Windows folder, and that I have to set the permissions on both systems in order to write to the Documents folder.
Maybe the documents folder isn't the documents folder?
Weird thing to say, I know, but I the name of the folder in Windows seems to change depending on the route used to access it. I know you said you changed permissions at the linux level, but Windows does with Documents / My Documents is weird, and maybe there's some daft interaction going on there ...
knowing "Windows", why would you expect *any* logic or consistancy? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-04-08 17:21, Marc Chamberlin wrote:
On 04/08/2018 03:10 AM, Carlos E. R. wrote:
That's not the full fstab line. It would be better if you posted the actual output of the "mount" command, the line pertaining to this mount point.
Hi Carlos - OK here is what the "mount" command shows. It actually shows the mount point twice because I do a bind mount of the root "/" to "/slash" -
mount | grep quantum /srv/autofs/auto.quantum.Win10 on /mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect) /srv/autofs/auto.quantum.Win10 on /slash/mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect)
(sorry these lines get broken up when doing a copy paste....)
You need an extension for Thunderbird, "Toggle Word Wrap" which allows you to write long lines. I was expecting to see like here (local mount): /dev/sda2 on /Windows/C type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096) See the user_id? What I don't see there is the remote mount of samba, how it is mounted from the remote machine. Your lines seem to be a local mount. Wait, I must be blind. Of course, you are not using the IPs, but the machine name auto.quantum.Win10. I see.
As I mentioned I don't mount these directly in fstab, but I use autofs instead. So I will give you full disclosure of the contents of the autofs configuration files so that you can fully understand how I am mounting the Windows file system. In the file /etc/auto.master the relevant line is -
/mnt/samba/Win10/quantum /srv/autofs/auto.quantum.Win10 --timeout=5 --ghost
That points to the actual mount configuration file (in a separate partition /srv so I can reuse it whenever I upgrade openSuSE) and the contents of /srv/autofs/auto.quantum.Win10 is what I previously showed you -
# # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage c -fstype=cifs,rw,dir_mode=0777,file_mode=0777,credentials=/etc/smb1.auth,uid=1000,gid=100,vers=2.0 ://quantumWin10/C
Well, as you can see the file mode/dirmode and uid do not appear in the mount command line output. Try not specifying them?
But I can see from the above that maybe only user 1000 will have write access.
And no, you can not change permissions with chmod on an ntfs disk.
And I agree with you, it doesn't make sense to me that doing a chmod on an ntfs disk would affect anything. But that is exactly what happened and hence my inquiry. I had tried everything I could think of on the Windows system (quantumWin10) directly, to open up C:/Users/marc/Documents to allow me to copy a file from my OpenSuSE laptop into that Documents directory, but nothing worked. What was even more surprising was that I could create a sub-directory - C:/Users/marc/Documents/tmp and was able to copy files there. I have been doing this as a workaround, hoping that someday this problem would get fixed in an update, but it never has. This problem goes way back and I have never bothered reporting it cause I can work around it, although it is a PITA. Anywise, I decided to try and tackle this problem again and this time I discovered that by changing the apparent permissions on my Linux laptop, on /mnt/samba/Win10/quantum/C/Users/marc/Documents from -r--r--r-- to -rw-r--r--, I was then able to copy files into the Documents folder from my OpenSuSE laptop! Totally surprised me because I did that on a whim without expecting it to work...
What this is saying to me is the Linux has a perspective of what the permissions are on mounted Windows NTFS file systems that is independent of actual permissions as understood by the Windows system. And that this *perceived* perspective must be changed also since it affects one's ability to access mounted Windows file systems. If I am right, then IMHO this is an extremely bad model, since it is totally confusing and NOT intuitively obvious on how to set permissions so as to make a mounted file system usable.
Mmm... :-? Maybe via samba you get different permission set than mounting locally a windows filesystem. This is something I haven't investigated.
From the responses I am getting here, my guess is that no one else has seen this, and yes for the most part accessing mounted file systems works for me as well. But this problem has showed up for my on all my Windows mounted file systems for the Documents folder so I don't know what to make of it. I can work around it, now that I know how, but it just seems very wrong that Linux is working with some sort of perceived permissions that are not related to the actual permissions of a Windows folder, and that I have to set the permissions on both systems in order to write to the Documents folder.
Thoughts? Marc....
Well, I don't have a windows machine permanently, so I don't have samba mounts to it. I can't try to replicate your setup. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 15.0, at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Sonntag, 8. April 2018, 17:21:20 CEST schrieb Marc Chamberlin:
On 04/08/2018 03:10 AM, Carlos E. R. wrote: [...]
mount | grep quantum /srv/autofs/auto.quantum.Win10 on /mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect) /srv/autofs/auto.quantum.Win10 on /slash/mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect)
(sorry these lines get broken up when doing a copy paste....)
/mnt/samba/Win10/quantum/c wasn't mounted when you did your "mount | grep...". Please do a "cd /mnt/samba/Win10/quantum/c" before so that the line starting with //quantumWin10/C will appear.
[...] That points to the actual mount configuration file (in a separate partition /srv so I can reuse it whenever I upgrade openSuSE) and the contents of /srv/autofs/auto.quantum.Win10 is what I previously showed you -
Even an fstab line wouldn't show all mount options that are actually used.
[...] Anywise, I decided to try and tackle this problem again and this time I discovered that by changing the apparent permissions on my Linux laptop, on /mnt/samba/Win10/quantum/C/Users/marc/Documents from -r--r--r-- to -rw-r--r--, I was then able to copy files into the Documents folder from my OpenSuSE laptop! Totally surprised me because I did that on a whim without expecting it to work... [...]
Isn't /mnt/samba/Win10/quantum/C/Users/marc/Documents missing the x bit, too? Without, you shouldn't even see its content. Actually, all directories should look like drwxrwxrwx because of your dir_mode. Gruß Jan -- Software stands between man and his machine. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/08/2018 12:14 PM, Jan Ritzerfeld wrote:
Am Sonntag, 8. April 2018, 17:21:20 CEST schrieb Marc Chamberlin:
On 04/08/2018 03:10 AM, Carlos E. R. wrote: [...]
mount | grep quantum /srv/autofs/auto.quantum.Win10 on /mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect) /srv/autofs/auto.quantum.Win10 on /slash/mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect) (sorry these lines get broken up when doing a copy paste....) /mnt/samba/Win10/quantum/c wasn't mounted when you did your "mount | grep...". Please do a "cd /mnt/samba/Win10/quantum/c" before so that the line starting with //quantumWin10/C will appear. Hi Jan, Ah! Good point!!! Ok I can do that.... cd /mnt/samba/Win10/quantum/c/Users/Marc/Documents/ marcslaptop:/mnt/samba/Win10/quantum/c/Users/Marc/Documents # mount | grep quantum /srv/autofs/auto.quantum.Win10 on /mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect) /srv/autofs/auto.quantum.Win10 on /slash/mnt/samba/Win10/quantum type autofs (rw,relatime,fd=37,pgrp=1452,timeout=5,minproto=5,maxproto=5,indirect) //quantumWin10/C on /mnt/samba/Win10/quantum/c type cifs (rw,relatime,vers=2.0,sec=ntlmssp,cache=strict,username=Marc,domain=QUANTUMWIN10,uid=1000,forceuid,gid=100,forcegid,addr=192.168.10.85,file_mode=0777,dir_mode=0777,nounix,mapposix,rsize=65536,wsize=65536,actimeo=1) //quantumWin10/C on /slash/mnt/samba/Win10/quantum/c type cifs (rw,relatime,vers=2.0,sec=ntlmssp,cache=strict,username=Marc,domain=QUANTUMWIN10,uid=1000,forceuid,gid=100,forcegid,addr=192.168.10.85,file_mode=0777,dir_mode=0777,nounix,mapposix,rsize=65536,wsize=65536,actimeo=1)
[...] That points to the actual mount configuration file (in a separate partition /srv so I can reuse it whenever I upgrade openSuSE) and the contents of /srv/autofs/auto.quantum.Win10 is what I previously showed you - Even an fstab line wouldn't show all mount options that are actually used.
[...] Anywise, I decided to try and tackle this problem again and this time I discovered that by changing the apparent permissions on my Linux laptop, on /mnt/samba/Win10/quantum/C/Users/marc/Documents from -r--r--r-- to -rw-r--r--, I was then able to copy files into the Documents folder from my OpenSuSE laptop! Totally surprised me because I did that on a whim without expecting it to work... [...] Isn't /mnt/samba/Win10/quantum/C/Users/marc/Documents missing the x bit, too? Without, you shouldn't even see its content. Actually, all directories should look like drwxrwxrwx because of your dir_mode.
Ok now I am really confused... I just did another ls -al so I could copy it and show you what I was seeing in the way of permissions settings... And now it is different and is showing what you said I should expect to see...
marc@marcslaptop:/mnt/samba/Win10/quantum/c/Users/Marc> ls -al | grep Document drwxrwxrwx 2 marc users 0 Apr 7 18:27 Documents drwxrwxrwx 2 marc users 16384 Apr 7 18:27 My Documents
But that is NOT what I was seeing this morning/last night when I reported this issue! Then I was just seeing that I had read permissions and I had to change the owner permission to include write in order to copy my files into the Documents folder... This is a head scratcher, is there some sort of time delayed effect going on? Got me beat! Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Sonntag, 8. April 2018, 22:01:57 CEST schrieb Marc Chamberlin:
On 04/08/2018 12:14 PM, Jan Ritzerfeld wrote:
Am Sonntag, 8. April 2018, 17:21:20 CEST schrieb Marc Chamberlin: [...] Hi Jan, Ah! Good point!!! Ok I can do that.... [...] //quantumWin10/C on /mnt/samba/Win10/quantum/c type cifs (rw,relatime,vers=2.0,sec=ntlmssp,cache=strict,username=Marc,domain=QUANTU MWIN10,uid=1000,forceuid,gid=100,forcegid,addr=192.168.10.85,file_mode=077 7,dir_mode=0777,nounix,mapposix,rsize=65536,wsize=65536,actimeo=1) [...]
fstype=cifs,rw,dir_mode=0777,file_mode=0777,credentials=/etc/ smb1.auth,uid=1000,gid=100,vers=2.0 Do you explicitly set SMBv2.002 because SMBv3.1.1 does not work? And dir_mode=0777,file_mode=0777 gives anyone on your computer access to all
The options looks fine. file_mode and dir_mode have no effect if Unix Extensions are used, so the presence of nounix was important. Since Windows doesn't support them, I expected nounix but it is still good to see. Back to your autofs.quantum.Win10: directories and files accessible by Marc.
[...]
Isn't /mnt/samba/Win10/quantum/C/Users/marc/Documents missing the x bit, too? Without, you shouldn't even see its content. Actually, all directories should look like drwxrwxrwx because of your dir_mode.
Ok now I am really confused... I just did another ls -al so I could copy it and show you what I was seeing in the way of permissions settings... And now it is different and is showing what you said I should expect to see...
Well, I think that's good! ;)
marc@marcslaptop:/mnt/samba/Win10/quantum/c/Users/Marc> ls -al | grep Document drwxrwxrwx 2 marc users 0 Apr 7 18:27 Documents drwxrwxrwx 2 marc users 16384 Apr 7 18:27 My Documents
But that is NOT what I was seeing this morning/last night when I reported this issue! Then I was just seeing that I had read permissions and I had to change the owner permission to include write in order to copy my files into the Documents folder... This is a head scratcher, is there some sort of time delayed effect going on? [...]
I've no idea. Even the default dir_mode=0755 should give you access to Documents. However, changing auto.quantum.Win10 AFAIK won't have any effect before autofs umounts after the timeout it and you mount it again. Gruß Jan -- Wisdom consists of the anticipation of consequences. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Marc Chamberlin <marc@marcchamberlin.com> [04-07-18 22:33]:
I wonder if some kind guru could explain this logic to me or direct me to an appropriate users group...
I have a mixed SOHO network in my home with both Linux and Windoz systems running on it. I use autofs to automount Windows folders on my Linux systems and for the most part I don't have any issues. But one thing that has been perplexing me is why I could not copy files from say my Linux laptop to my Windows system at the C:/Users/marc/Documents folder. (I automount C: using autofs under /mnt/samba/windowscomputername/C so I can have access to the entire drive from my laptop) What really perplexed me was that I could copy files to any subfolder under C:/Users/marc/Documents such as to C:/Users/marc/Documents/tmp/newfile. My instincts told me there had to be some sort of permission problem that I had to resolve on the Windows system. So I tried everything I could think of to relax the permissions so that anyone and everyone could access the Documents folder, but to no joy.
It finally occurred to me to try and take a look at it from the Linux side, so using Dolphin I examined the permissions of the Documents folder and sure enough Dolphin was reporting that I only had read permissions on the Documents folder. So on a lark I decided to try and change the permissions via Dolphin (chmod also behaved the same way) to give me read/write permissions and I will be damned if that didn't work! But I will be twitched if I can understand why in the world that worked and why I have to give myself permission to write to the Documents folder on a Windows system, from/on the Linux system side also! Shouldn't file permissions and access be strictly governed by the system that owns the files and folders? Why does a Linux system user have to give himself/herself permissions in order to write to files on a different system? This is effectively saying that in order to write to a file system on another computer I have to give myself permission to do so on BOTH systems! In other words, it wasn't Windows that was blocking me from writing to the Windows file system from my Linux laptop, it apparently was Linux itself! Is there some weird magic about Documents folders on Windows systems? Doesn't make any sense to me...
Just to be certain, I took a look at the folder permissions, under Windows, both before and after making the permission change on the Linux system, and I could not see any changes so this appears to be strictly a Linux side permissions issue...
I do not understand your mounting, but.... I use a cifs mount from linux to windows and can move files both ways: from fstab (one line): //192.168.1.14/C-Share/ /home/paka/cifs cifs credentials=/root/.smbcredentials,guest,nofail,_netdev,iocharset=utf8,sec=ntlmssp,uid=1000,gid=100,file_mode=0777,dir_mode=0777,vers=2.1 0 0 it has been a while but you must make the .smbcredentials file. I cobbled this all together googling. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Anton Aylward -
Carlos E. R. -
Doug -
Jan Ritzerfeld -
Marc Chamberlin -
Patrick Shanahan -
Wols Lists