From owner-freebsd-hackers  Tue May  2 20:37:39 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id UAA26879
          for hackers-outgoing; Tue, 2 May 1995 20:37:39 -0700
Received: from caern.protocorp.com ([198.147.97.66])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA26870
          for <hackers@freebsd.org>; Tue, 2 May 1995 20:37:28 -0700
Received: from caern.leonardo.net (localhost [127.0.0.1]) by caern.protocorp.com (8.6.9/8.6.9) with ESMTP id WAA00370; Mon, 1 May 1995 22:15:26 -0700
Message-Id: <199505020515.WAA00370@caern.protocorp.com>
To: terry@cs.weber.edu (Terry Lambert)
cc: hackers@FreeBSD.org
Subject: Re: Compress dumps? 
In-reply-to: Your message of "Mon, 01 May 1995 11:29:46 MDT."
             <9505011729.AA07524@cs.weber.edu> 
Date: Mon, 01 May 1995 22:15:26 -0700
From: "Mike O'Brien" <obrien@leonardo.net>
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> One possible fix is to go to a block compression scheme or a file
> compression scheme as the tapes are written.

This is more what I had in mind.  I fully recognize the danger in
simply gzipping the entire stream.  I was just wondering if the notion
had occurred to anyone else.  Given my experiences in the use of
"floppy tape" I must say that rather than saving money by compressing
the dump stream, I'm more of a mind to save my sanity by using a real
SCSI tape drive so I don't have to worry about false economy.

Mike O'Brien