From owner-freebsd-hackers Mon Mar 13 17:40:52 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA04733 for hackers-outgoing; Mon, 13 Mar 1995 17:40:52 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA04727 for ; Mon, 13 Mar 1995 17:40:51 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id RAA01457; Mon, 13 Mar 1995 17:40:45 -0800 From: Poul-Henning Kamp Message-Id: <199503140140.RAA01457@ref.tfs.com> Subject: Re: install compressed binary patch To: davidg@Root.COM Date: Mon, 13 Mar 1995 17:40:45 -0800 (PST) Cc: kargl@troutmask.apl.washington.edu, freebsd-hackers@freefall.cdrom.com In-Reply-To: <199503140135.RAA00511@corbin.Root.COM> from "David Greenman" at Mar 13, 95 05:35:19 pm Content-Type: text Content-Length: 918 Sender: hackers-owner@FreeBSD.org Precedence: bulk > The gzip binary idea was added so that we could fit more on the install > floppies. I don't recall anyone ever suggesting that you might want to use > this to compress your system binaries to save hard disk space. This doesn't > seem very wise to me. > The only reason I've said anything at all about this is that I'm concerned > about the potential for future bugs reports from people that don't understand > the ramifications involved with using gziped binaries. Well, >I< have said something about using them to save space. On my 130Mb handbook, I saved close to 7 mb by compressing things like troff and perl, which are not used too often, but too good to throw away. But yes, you need to understand the ramifications... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'