Davide Guarisco wrote: > Suddenly, I cannot mount one share I have been mounting before with no > problems. > When I connect to the server from the CIFS browser, a folder containing a > list of aliases to the server's shares opens up (as usual). When I > double-click the share I want to connect to, I get an error message: The alias > "xyz" could not be opened, because the original item cannot be found. > > Any ideas?
That's a combination of a problem in Sharity and a kind of bug in Finder. Sharity must have had a transient problem and Finder tends to cache it. It's very hard to get this idea of a broken alias out of Finder's head. You can try restarting Finder (e.g. with Command-Alt-ESC). If this does not help, try a reboot. If it still does not help, there may be a stale folder in /Volumes. This problem will hopefully go away in 2.7. We let autodiskmount do the job of folder creation and deletion in /Volumes since 2.7 beta 4. > Mounting the share manually works! > > One other problem I am having when mounting the shares manually (for example, > mount points that I have stored), is that I get an error message telling my > that I am not the owner of the directory in the /Volumes folder. What I do > then, is to create a folder with the same name as the mount point inside the > /Volumes folder. Upon clicking Mount, Sharity replaces the folder with an > alias and everything works. It's only a little cumbersome to always have to > create a folder before mounting a share. > > Maybe one other possibility to make this work automatically would be to change > the ownership of the /Volumes folder. I have been hesitant to do this, as it > may interfere with the system operation. Is there any drawback in changing > ownership of the /Volumes folder? Would this fix the error message? Manual mounting has not been made for mounting in /Volumes and I would not recommend it. Simply make a folder in your home directory where you mount CIFS shares. Changing the owner of /Volumes should do not much harm and you can change it back if required. However, you never know the actual effect of such a change. Also, the OS might change the ownership back on each reboot. Sharity's permission check for mounting might be a bit too restrictive. We have decided for checking ownership instead of write permissions because somem operating systems which allow NFS mounts by users do it this way. We preferred security over flexibility in this case. Regards, Christian. -- Dipl.-Ing. Christian Starkjohann Objective Development mailto:[EMAIL PROTECTED] | http://www.obdev.at/ _______________________________________________ Sharity-talk mailing list [EMAIL PROTECTED] To unsubscribe see http://at.obdev.at/mailman/listinfo/sharity-talk
