Looking back on my original post I did use those options: mount -t smbfs -o username=user,password=short-password,dir_mode=0555,file_mode=0555 //ip/share /media/folder
I can't seem to replicate the behavior at the moment (un-commenting old code dose not have the same effect as before) I'm assuming it was fixed some time between Aug 20 2008 (v2.6.24-19) and Jan 28 2010 (v2.6.28-18). mount.cifs //ip/share /media/folder -o file_mode=0555,dir_mode=0555,r,username=user,password=short-password also works. thanks for the help anyway, feel free to close the bug. On Thu, Mar 11, 2010 at 7:39 AM, Thierry Carrez <[email protected]>wrote: > Those are documented on mount.cifs manpage: > http://manpages.ubuntu.com/manpages/lucid/en/man8/mount.cifs.8.html > > -- > mount smbfs not working properly after upgrade from 6 to 8 > https://bugs.launchpad.net/bugs/268536 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “samba” package in Ubuntu: Incomplete > > Bug description: > objective : mount the same SMB share to 2 folders with different > permissions. > > history: was working before upgrade to v8. Did not find any solutions on > the web. > > problems: > 1) mounting the same SMB share the second time changes the dmask on the > first share. > 2) mounting the same SMB share the second time fails with: folder dose > not exist. > 3) mount --bind ignores fmask and file_mode / dmask and dir_mode > 4) chmod is able to change permissions on mounts > 5) files are created with wrong permissions re: fmask > > temporary workarounds: ? > > solutions:? > > origonal example: http://ubuntuforums.org/showthread.php?t=911549 > > cat /proc/version > Linux version 2.6.24-19-generic (bui...@terranova) (gcc version 4.2.3 > (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Aug 20 22:56:21 UTC 2008 > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/samba/+bug/268536/+subscribe > -- mount smbfs not working properly after upgrade from 6 to 8 https://bugs.launchpad.net/bugs/268536 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
