[tahoe-dev] Proposed short description of tahoe-LAFS for personal backup

[Greg Troxel]

Saint Germain <saintger at gmail.com> writes:

>> Also, while tahoe works well, I don't think anyone thinks it is
>> reasonable to keep data only in tahoe.  This is especially true if one
>> enables expiration.
>> 
>
> Ok I'll change accordingly !

You may want to wait for others to speak up; my opinion may be
controversial and not shared.

>> >   - Works on Linux, Mac OS X and Windows. I have however a few
>> > doubts on the Windows compatibility for managing locked files. But
>> > you can use Duplicati which uses Windows VSS and can use tahoe-LAFS
>> > as backend.
>> 
>> It also works fine on NetBSD.  It probably works on other BSDs.
>
> Unix-like is the appropriate word then ?
> I never know the proper expression (linux, Gnu/linux, BSD*, etc.)

One way is "reasonable POSIX-like operating system", and I think that's
accurate.

But if you're going to list specific systems, then I was pointing out
one that you left out (I maintain the pkgsrc (portable packaging system
that is standard on NetBSD) entry for tahoe).  There's a big difference
between programs that are in theory portable to any POSIX-compliant
system, and programs that are known to work on multiple systems; tahoe
is one of the latter.

>> I don't know what you mean about locked files.  If you mean locking
>> like in NFS and lockd/statd, then I wouldn't expect that to work
>> anywhere.
>> 
>
> I'm talking about this problem :
> http://backuppc.sourceforge.net/faq/limitations.html#locked_files_are_not_backed_up
>
> BURP for instance if managing that with Windows VSS (and I suppose so
> is Duplicati).

I see.  I have no idea about anything on Windows :-)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120613/4e0189fc/attachment.pgp>