From owner-freebsd-current Mon Sep 21 20:38:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03832 for freebsd-current-outgoing; Mon, 21 Sep 1998 20:38:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03800 for ; Mon, 21 Sep 1998 20:38:18 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id UAA25511; Mon, 21 Sep 1998 20:38:28 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: dan@math.berkeley.edu (Dan Strick) cc: current@FreeBSD.ORG Subject: Re: SNAP Status In-reply-to: Your message of "Mon, 21 Sep 1998 19:28:52 PDT." <199809220228.TAA20688@math.berkeley.edu> Date: Mon, 21 Sep 1998 20:38:28 -0700 Message-ID: <25507.906435508@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I tried the same thing: > > cat bin.?? | zcat | tar tvf - > > and it worked just fine (i.e. I saw no error messages though I did not > check the pipeline return status). The problem seems to be in the > installation process itself. It claimed the extraction failed but > gave no reason. Is the error output from the extraction commands stored > anyplace during the installation process? (Someplace that I could > look at after the failure?) John Hay found it earlier today and I fixed it. It was switching to minigzip that hosed us (dark look at Dima ;) and I failed to adequately ensure that it would be truly equivalent. My bad. I'm rolling another SNAP now. current.freebsd.org is also back up but behaving a little oddly; I'm working it too now. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message