Hi Thierry, I tried what you suggested and had the same problem. However, I did discovered something. It seems that it is the *name* of the share that is causing the problem rather than what it is pointing to. On my system, anything shared using the name "shared" is read-only, whether it points to a folder (i.e., /home/scott/real) or a symlink (i.e., /home/scott/shared). The smb.conf entry above is read-only from my windows machines (I've tried it from two different machines). However, if I simply change the name of the share to "shared2" then it works as expected, i.e., I change it to read:
[shared2] path = /home/scott/shared writeable = yes browseable = yes valid users = scott I've looked through my smb.conf file and there are no other instances of "shared" other than that above. Also, the read-only problem is happening from two different windows computers. So, I think it's still something happening on the server side. Is it possible that samba has some other configuration information somewhere or that "shared" is somehow reserved? Any other ideas to try? Thanks, -- Scott -- samba shares of symlinks are always read-only https://bugs.launchpad.net/bugs/380715 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
