From owner-freebsd-hackers Thu Aug 15 08:27:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA15193 for hackers-outgoing; Thu, 15 Aug 1996 08:27:00 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA15188 for ; Thu, 15 Aug 1996 08:26:57 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id LAA04835; Thu, 15 Aug 1996 11:26:34 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Michael Searle cc: hackers@freefall.freebsd.org From: "Gary Palmer" Subject: Re: Nightmare In-reply-to: Your message of "Thu, 15 Aug 1996 14:37:39 -0000." Date: Thu, 15 Aug 1996 11:26:34 -0400 Message-ID: <4832.840122794@orion.webspan.net> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Searle wrote in message ID : > There are similar things on the Acorn that can handle arc files and tar.gz > files, but it is very slow for tar.gz as the whole archive has to be read or > written at any access. You could get around this by using a gz.tar file > (with tar's blocksize changed to the disk's frag size), but a whole > compressed FS (like Doublespace etc. for DOS) would be better than either. Theoretically, if you handled large files in the archive, it would be possible to compress the individual files rather than the entire archive (and not loose too much in terms of compression, and gain a lot in terms of access). ArcFS *MAY* have done something like this for some of it's compression. I know that using tar for a read-write archive is MURDER :-( (Yes, I own an Arc :-) ) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info