From owner-freebsd-questions Wed Nov 12 12:58:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA08325 for questions-outgoing; Wed, 12 Nov 1997 12:58:38 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08319 for ; Wed, 12 Nov 1997 12:58:32 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.8.7/8.6.9) with ESMTP id VAA29711 for ; Wed, 12 Nov 1997 21:58:00 +0100 (CET) Message-Id: <199711122058.VAA29711@peedub.muc.de> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-questions@freebsd.org Subject: Re: gzipped programs Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 12 Nov 1997 10:44:18 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Nov 1997 21:57:59 +0100 From: Gary Jennejohn Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Scott Morris writes: >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) >> take a look at /sys/i386/conf/LINT, specifically: pseudo-device gzip #Exec gzipped a.out's --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com