From owner-freebsd-current  Sun Dec 14 13:11:10 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id NAA11003
          for current-outgoing; Sun, 14 Dec 1997 13:11:10 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA10970
          for <current@FreeBSD.ORG>; Sun, 14 Dec 1997 13:11:05 -0800 (PST)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id WAA13252;
	Sun, 14 Dec 1997 22:08:25 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: John Polstra <jdp@polstra.com>
cc: Eivind Eklund <perhaps@yes.no>, current@FreeBSD.ORG
Subject: Re: problems with gzip'd executables 
In-reply-to: Your message of "Sun, 14 Dec 1997 11:59:40 PST."
             <199712141959.LAA20309@austin.polstra.com> 
Date: Sun, 14 Dec 1997 22:08:25 +0100
Message-ID: <13250.882133705@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In message <199712141959.LAA20309@austin.polstra.com>, John Polstra writes:

>Meanwhile, it turns out that the gzipped executable problem was
>really a bug in imgact_gzip.c.  So I committed a fix for that.

Actually it was done deliberately that way under the assumption that
nobody would ever want to touch the a.out header of a running 
program :-)

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."