From owner-freebsd-current  Sun Dec 14 14:11:38 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA15180
          for current-outgoing; Sun, 14 Dec 1997 14:11:38 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from zippy.dyn.ml.org (garbanzo@haiti-68.ppp.hooked.net [206.169.228.68])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA15161
          for <current@FreeBSD.ORG>; Sun, 14 Dec 1997 14:11:32 -0800 (PST)
          (envelope-from garbanzo@hooked.net)
Received: from localhost (garbanzo@localhost)
	by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id OAA08976;
	Sun, 14 Dec 1997 14:12:34 -0800 (PST)
X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs
Date: Sun, 14 Dec 1997 14:12:34 -0800 (PST)
From: Alex <garbanzo@hooked.net>
X-Sender: garbanzo@zippy.dyn.ml.org
To: John Polstra <jdp@polstra.com>
cc: current <current@FreeBSD.ORG>
Subject: Re: problems with gzip'd executables 
In-Reply-To: <199712141959.LAA20309@austin.polstra.com>
Message-ID: <Pine.BSF.3.96.971214141024.256D-100000@zippy.dyn.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Sun, 14 Dec 1997, John Polstra wrote:

> > Personally, I feel that you should just drop the hacks to
> > handle old emacs binaries and send a clear heads-up to
> > current@FreeBSD.ORG. Current is for developers - we should have the
> > hardware to handle an Emacs re-compile :-)
> 
> I agree with you.  I would like to put a patch into the emacs port
> before I back out the ld.so hack, though.  I probably can't get around
> to doing that for about a week.  I have the patch, but I don't have
> any more time to spend on this until next weekend.

I agree with you guys here too.  Running -current, recompiling a few
programs isn't supposed to be unexpected.  Afterall with the procfs
changes I've recompiled w, ps, and top (and my lkms) quite a few times.
100% binary compatibility isn't the goal (I think).

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

Thanks for committing a fix.  I'll grab it in my nightly cvsup.

- alex