Thanks, Dan. Here is a snippet of my smb.conf for the Samba server serving the home shares: [global] unix extensions = yes case sensitive = yes delete readonly = yes
dos charset = unix charset = UTF8 [homes] path = /home/users/%U profile acls = Yes ea support = yes map archive = no map hidden = no map read only = no I mount the home share under Ubuntu using pam_mount.so when I log in. Here is the pam_mount.conf.xml snippet: <volume fstype="cifs" server="san01" path="%(USER)" mountpoint="~" options="soft,nomapchars" /> Here is what the man page for mount.cifs says for mapchar and nomapchar: mapchars Translate six of the seven reserved characters (not backslash, but including the colon, question mark, pipe, asterik, greater than and less than characters) to the remap range (above 0xF000), which also allows the CIFS client to recognize files created with such characters by Windows´s POSIX emulation. This can also be useful when mounting to most versions of Samba (which also forbids creating and opening files whose names contain any of these seven characters). This has no effect if the server does not support Unicode on the wire. nomapchars Do not translate any of these seven characters (default) Also for completeness (I guess) > sudo cat /proc/fs/cifs/LinuxExtensionsEnabled 1 So with all that I still get the following: rwsm...@pc-ubuntu-01:~$ > "colon:" bash: colon:: No such file or directory and rwsm...@pc-ubuntu-01:~$ ln -s ../rwsmith Symlink_to_myself rwsm...@pc-ubuntu-01:~$ ls -ld Symlink_to_myself lrwxrwxrwx 1 rwsmith rwsmith 10 2009-06-22 16:21 Symlink_to_myself -> ../rwsmith rwsm...@pc-ubuntu-01:~$ cd Symlink_to_myself rwsm...@pc-ubuntu-01:~/Symlink_to_myself$ pwd /home/users/rwsmith/Symlink_to_myself Looks like symlinks are working which might imply that Unix Extensions were negotiated? Is there any place to look to verify if the share session negotiate the Unix Extenstions and what capabilities were negotiated? I guess this is more of a Samba issue at this point but I have not heard a peep from my post on the Samba list. Bob --bs On Mon, Jun 22, 2009 at 12:54 PM, DanKegel <[email protected]> wrote: > > On Jun 21, 7:28 pm, DanKegel <[email protected]> wrote: > > > I can not run Picasa (and for that matter Wine) when my home folder is > > > mounted using smbfs/cifs and the backend server is Samba v3.3. The > > > problem appears to be related to the symbolic links in the ~/.google/ > > > picasa/3.0/dosdevices folder where the file names include the colon > > > ":", eg. c:, d:, d::, etc. This wasn't problem in past when my home > > > folder was NFS mounted. > > > > > The server is Fedora 11 running Samba 3.3 and my workstation is > > > running Ubuntu Karmic Koala (latest). > > > > That's very interesting. I've posted a note to wine-devel to let them > > know about the problem. Maybe we can find a workaround > > (like having wine fall back to using underscores instead of colons). > > Please make sure the server has the CIFS Unix Extensions turned > on. I hear that is required for both symlinks and for filenames > containing > colons. Also make sure you're mounting with cifs rather than smbfs. > - Dan > > > > -- Robert W. Smith BISLink Internet Service --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google-Labs-Picasa-for-Linux" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Labs-Picasa-for-Linux?hl=en -~----------~----~----~----~------~----~------~--~---
