hey greg,
yeah you are right, i used osxfuse & the respective sshfs.
the thing is that once i mount a tahoe volume, which i do like this:
mkdir /Volumes/tahoe-test
sshfs -p 8022 username@127.0.0.1:8022 /Volumes/tahoe-test
-oauto_cache,reconnect,volname=volumename
The whole finder gets quite unresponsive. i would understand if just accessing
the tahoe volume would cause some delays, but i dont understand why the whole
Gui is affected.
No idea if this is a bug in osxfuse or if i am doing something wrong, but it
makes this approach kind of unusable for me.
ciao,t.
________________________________
From: Greg Troxel <g...@ir.bbn.com>
To: til <til...@yahoo.com>
Cc: Tahoe-LAFS development <tahoe-dev@tahoe-lafs.org>
Sent: Thursday, June 13, 2013 1:31 PM
Subject: Re: [tahoe-dev] git-annex & tahoe
til <til...@yahoo.com> writes:
> hey people,
>
> after my unsuccesful or mostly unsuccesful excursions of the sort of
>
> - connect owncloud to tahoe via sftp
> - connect owncloud to tahoe via ftp
> - connect my mac to tahoe using macfuse & sshfs (too slow!)
> - compile csync on my mac to use it with tahoe via sftp
[digression:
Do you really mean macfuse? That's no longer being maintained:
https://code.google.com/p/macfuse/
I have seen
http://osxfuse.github.io/
http://fuse4x.github.io/ (competing fork, now merged into osxfuse, yay)
and maybe this is the same thing too:
http://sourceforge.net/projects/fuse-for-macosx/
]
Can you explain what you mean by "slow"? Are operations with
sshfs/sftp/tahoe slower than using the tahoe CLI?
(I have found tahoe to be slow enough that I'd only want to use it for
backups.)
_______________________________________________
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
