From owner-freebsd-chat Sat Dec 21 21:05:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA19257 for chat-outgoing; Sat, 21 Dec 1996 21:05:57 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA19251 for ; Sat, 21 Dec 1996 21:05:55 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id VAA12874; Sat, 21 Dec 1996 21:05:34 -0800 (PST) To: dg@root.com cc: "Jonathan M. Bresler" , marcs@znep.com (Marc Slemko), jfieber@indiana.edu, freebsd-chat@freebsd.org Subject: Re: EDO parit RAM (Was Re: Tyan ...) In-reply-to: Your message of "Sat, 21 Dec 1996 19:22:24 PST." <199612220322.TAA21892@root.com> Date: Sat, 21 Dec 1996 21:05:34 -0800 Message-ID: <12870.851231134@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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