From owner-freebsd-questions Wed Nov 12 07:42:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA11810 for questions-outgoing; Wed, 12 Nov 1997 07:42:15 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from tsi.gte.com ([205.174.176.40]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA11803 for ; Wed, 12 Nov 1997 07:42:11 -0800 (PST) (envelope-from smorris@tsi.gte.com) Received: from iiohab.tsi.gte.com by tsi.gte.com (5.x/SMI-SVR4) id AA28767; Wed, 12 Nov 1997 10:46:07 -0500 Date: Wed, 12 Nov 1997 10:44:18 -0500 (EST) From: Scott Morris To: steve howe Cc: questions@FreeBSD.ORG Subject: Re: gzipped programs In-Reply-To: <19971112120034.9434.qmail@hotmail.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve, You can pretty much assume that if you gzip a file in the bin directories it will be a Bad Thing(tm). The level of badness will depend on the particular file you zip. You really don't gain much if anything by compressing binaries anyway. You can compress old logfiles and such but stay away from configs etc. Of course if you installed the source you can compress or remove it if you need the space. Scott On Wed, 12 Nov 1997, steve howe wrote: > is there any way i can tell if gzipping a program > will do damage to my system without resorting to > trial and error? > > i was really crammed for space on one system, and > decided to gzip some executables, and found many > programs in /bin, /sbin, /usr/sbin that cause > this system to crash when gzipped. (2.2.2) > > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > ----- Scott Morris GTE Telecommunication Services Inc. Information Security smorris@tsi.gte.com