Date: Sat, 21 Dec 1996 21:05:34 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: dg@root.com Cc: "Jonathan M. Bresler" <jmb@freefall.freebsd.org>, marcs@znep.com (Marc Slemko), jfieber@indiana.edu, freebsd-chat@freebsd.org Subject: Re: EDO parit RAM (Was Re: Tyan ...) Message-ID: <12870.851231134@time.cdrom.com> In-Reply-To: Your message of "Sat, 21 Dec 1996 19:22:24 PST." <199612220322.TAA21892@root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> useless. If we were to change it to a one-per-file scheme, it wouldn't be > such a big effort to keep the stuff in sync (hint: I very much dislike > copying several giant multi-megabyte files over to wcarchive continuously). Don't worry, I wasn't contemplating the latter scenario under any circumstances. That's why I asked the question in terms of what tool would be used and suggested rsync as the first candidate - no sensible protocol does whole-file transfers, it figures out that there was an append operation and only sends the new stuff. CVSup is another candidate in this category. However, though it's technically possible to sync the One Big File archives to wcarchive in a reasonably non-crazed way, I still agree with David that the storage format is, at best, highly unwieldy and non-conducive to indexing. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12870.851231134>