I have a lot of links to my previous fstab mounts in various applications, so I decided to ease the transition by deleting the mount point folders (mine were in /mnt) and creating symbolic links to the hidden gvfs share directories:
Of course you could do the same thing in your home directory:Code:
sudo ln -s ~/.gvfs/'sharename on server' /mnt/sharename
The next thing that I really need to verify is that files that I create on these shares are accessible to other users (I had to force 777 permissions on my NAS drives in fstab before).Code:
ln -s ~/.gvfs/'mp3s on server' ~/Music/shared
Perhaps the next thing to test is whether that annoying gedit bug that complained so loudly when saving files on Samba shares is also resolved in gvfs (I expect that it will be).
I did just run into a situation that gave me some trouble, however. I tried to mount a disk image on one of my remote shares using Unetbootin, but it couldn't see my symbolic links and even more strangely the .gvfs directory was also not visible in my home directory. The same thing happens with gedit, so it's not just a Unetbootin issue. It appears that when programs run as root they don't have access to these shares.
That could be problematic at times, but there's probably a way to work around it (by mounting the share manually, I assume).
I also think it's odd that I don't experience the gedit bug now, given that these shares are still mounted via Samba. Anyone else who knows this bug want to give this a shot? I definitely still had them when I first installed Jaunty and I was mounting them using CIFS via fstab.
There is already a list of shares in the keyring...
for obj in gnomekeyring.find_network_password_sync(None,None,None,None,"smb"):
mount = "%s://%s:%s@%s" % (obj["protocol"], obj["user"], obj["password"], obj["server"])
if __name__ == '__main__':
Well, I am a pretty heavy user of my file shares. I'm often reading/writing large amounts of data to and from the shares. Already, in the past 2 days, I've had dbus-gvfs hang on me once, and I've had gvfs just drop the mount 4 - 6 times.
I'm not particularly frustrated because I've always had problems between Ubuntu and a SMB server when heavily accessing large files. It works fine on the same computer Vista > SMB.
Of course, if anyone has any suggestions or troubleshooting steps I'd be glad to hear them.
The file manager in MS Windows has a nice feature called "Map Network Drive". This allows you to permanently assign Samba shares to a drive letter which any program can access. It can be made persistent across reboots. This feature is tremendous when you have a Samba server on your network that has files you need to continuously access.
I followed this to a "T" and it didnt work... no mount... any suggestions..??