search for: superlifter

Dear List, I just googled "superlifter" and found below link, but I can't get any source code. http://superlifter.sourceforge.net/ Any help or info on this is mostly appreciated. And sorry for the trouble, if it's NOT allowed to post here. THanks. -- Daniel

...ed to be concerned with reading or writing security information. It may need to have attribute/information "meta" files to assist in delivering consistent cross platform information. I plan to post a bit more about that in response to some questions raised from my previous post about superlifter and OpenVMS. -John wb8tyw@qsl.network Personal Opinion Only

> From: jw schultz <jw@pegasys.ws.invalid> > > On Fri, Jul 26, 2002 at 09:03:32AM -0400, Bennett Todd wrote: > >>2002-07-26-03:37:51 jw schultz: >> >>>All that matters is that we can represent the timestamps in >>>a way that allows consistent comparison, restoration and >>>transfer. >> >>A very good statement indeed. There are

Hey everyone, I am a final semester MCA student. I've chosen rsync as the subject of my project for my graduation. Hence I would appreciate it if someone could guide me with some ideas on how I can contribute to rsync. I will work hard to implement whatever suggestions that you can all give me. I would definitely like to know what are some of the issues concerning rsync. May be I can then

> Qualities > > 1. Be reasonably portable: at least in principle, it should be > possible to port to Windows, OS X, and various Unixes without major > changes. In general, I would like to see OpenVMS in that list. > Principles > > 1. Clean design rather than micro-optimization. A clean design allows optimization to be done by the compiler, and tight optimization

...s sense, because I'm trying to present the remote system as a local filesystem. I still have a lot of things to go, however before I get too far into it, I want to check in with the rsync gods about future direction. I take it that most of the future work is going to be on something called superlifter, and that major changes to rsync are not expected. So a significant re-architecting of the rsync code into a library isn't likely. The major problems with just wrapping the rsync binary are that: * It is really inefficient, especially with large files, because I'm downloading the remote...

I am rsyncing several hunderds of thousands of files in several directories. The way I got rsync to work for me was I wrote a script which NFS mounts the directory I am rsyncing first before starting, and then it goes through the directories and rsyncs them in bite sizeable chunks by going a few directories deep and starting there.. Is there any way to have this as an option inside rsync

Hello, I'm currently evaluating the possibility of implementing a rsync client in a project for my company. The platform used is currently not supported and implementing the client from scratch currently seems to be the most feasible approach. For that I'd be very much interested in a description of the protocol that rsync talks on port 873. Is such a description available somewhere? I

Hi there, I haven't yet delved into the rsync source code, and thus would need to ask a few questions first before going into the wrong direction. We have not, one but several cases[1] of doing Disaster Recovery type backup/synchronization with typically 1 to 2 million of files. Now yes, I know I can go and write a perl/python/<flavour_of_the_year> script to recursively do the

For the small number of people who are checking this out, I released version 0.05 a couple days ago (and only mentioned it on my new-protocol web page) followed today by 0.06. Some highlights of the two releases: - We handle symlinks now in our recursive synchronization mode. - Directory scanning is no longer limited to one active directory at a time (which was sorely needed when all the

I'm interested in these very questions (librsync-rsync relationship, remaining limitations of rsync, active prospects for ground-up rewrites), Google searches for rsync info have proved a little too vague due to the programs ubiquity. Much has certainly changed since this was written, could some people with knowledge in these areas could update martin's response for the state of rsync,