-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the delayed response.
I have verified that the update was visible and have updated the Wiki.
Thank you for your help!
On 5/29/2014 9:37 AM, Marina Brown wrote:
> On 05/28/2014 09:21 PM, Paul Rabahy wrote:
>> Thank you very much. Can you poi
On Sun, Jun 01, 2014 at 11:11:29AM -0400, Greg Troxel wrote:
> David Stainton writes:
>
> > Since Tahoe-LAFS is not a posix compliant filesystem...
> > we cannot easily create a persistent volume that only
> > stores data on a Tahoe grid. There is an ugly FUSE hack
> > but it is extremely ineffie
David Stainton writes:
> Since Tahoe-LAFS is not a posix compliant filesystem...
> we cannot easily create a persistent volume that only
> stores data on a Tahoe grid. There is an ugly FUSE hack
> but it is extremely ineffient.
This can be viewed as a bug in tahoe :-)
But seriously, fixing the F
Hi Daira,
Thanks for all the info!
> +1. There are two existing tickets about scheduled backups:
=-)
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/643
I reviewed this ticket and thought about it too.
It doesn't seem appropriate for what I had in mind...
and there may be problem/solution conf
>> 1. the Tahoe-LAFS debian package:
>>
>> This part is done. Great!
>>
> Congratulation :)
> Tahoe documentation could mention this:
> https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/quickstart.rst
OK... I volunteer to update
https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/quickstart.rst