If I mount an Samba resource from the server with: mat@second mat $ smbmount //main/download mnt Password: It works just fine. But after that when I try to unmount it: mat@second mat $ smbumount mnt You are not allowed to umount /home/mat/mnt It just don't work. After I try: mat@second mat $ su Password: root@second mat # smbumount mnt It's OK. Samba executables permissions are set as default: root@second mat # ls -al `which smbmount` -rwxr-xr-x 1 root root 647828 2004-01-27 13:19 /usr/bin/smbmount root@second mat # ls -al `which smbumount` ---s--x--x 1 root root 7064 2004-01-27 13:19 /usr/bin/smbumount root@second mat # ls -al `which smbmnt` ---s--x--x 1 root root 9172 2004-01-27 13:19 /usr/bin/smbmnt The problem is it worked fine on x86 but it just doesn't work on my new PPC installation. The Samba version is: root@second mat # qpkg -I -v samba net-fs/samba-3.0.1-r1 * One more thing - I've got the exactly same message on other PPC machine (current one is Pegasos II, the first one os IBM's B50 Server) on other distro. But as the problem wasn't critical (as it is now - quite a few of my scripts need to be corrected tu use sudo or something ;)) I didn't investigated. ANd finally - I've found some patch on some japanese page which suggests that the problem can be using 32/16 bit uids in Samba. The URL of the patch (as I'm not really that good at programming ;)) is: http://ring.fujixerox.co.jp/archives/net/samba-jp/patch/2.0.7/smbmount-2.0.7-includes.patch
what about with new samba versions? some uid/gid issues in ppc were lately resolved (yes, this post comes a bit late, I know ;) )
closing for now: 16/32 bit gid/uid was fixed some versions ago. Reopen if needed
I've just installed 3.0.7 (after emerge sync) - it works fine now. It's really unfortunate that since 3.0.5 there was no version that would be marked even unstable for ppc - all versions up to my last emerge sync (which I did some two weeks ago) didn't have ppc keyword so I didn't noticed that the problem was solved in 3.0.5-r1.
