>
>> And what about rsync3 support in File::RsyncP ?
>>      
> There's progress.  Most of my BackupPC work recently has been on 4.x,
> the next major version.  Several months ago there were various emails
> about the architecture.  Yes, it will support rsync 3.x and extended
> attributes.  I've taken a different approach for rsync support and
> File::RsyncP is no longer used.  The new setup uses a slightly modified
> native rsync 3.x on the server side, with a perl emulation layer on all
> file system IO that maps to the BackupPC store.  The advantage is all
> the usual rsync options are available, and it's native C code (until it
> hits the perl emulation layer of course).
>
> And, yes, there will be no hardlinks in 4.x...
>
>    

I should probably look back at the archives for this, but "no 
hardlinks"?   I thought that was the way the pool was able to save disk 
space -- an essential feature (at least for us).  Is this going to be 
implemented in some other way?


Trey Nolen


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/