From owner-freebsd-bugs  Tue Jun 20 06:48:53 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id GAA20936
          for bugs-outgoing; Tue, 20 Jun 1995 06:48:53 -0700
Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA20929
          ; Tue, 20 Jun 1995 06:48:41 -0700
Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id OAA13628; Tue, 20 Jun 1995 14:48:34 +0100
X-Authentication-Warning: whisker.internet-eireann.ie: Host localhost didn't use HELO protocol
To: "Stephen F. Combs" <test-owner@salem.ge.com>
cc: FreeBSD-hackers@freefall.cdrom.com, FreeBSD-bugs@freefall.cdrom.com
Subject: Re: Problems with Installing 2.0.5R 
In-reply-to: Your message of "Tue, 20 Jun 1995 08:42:40 EDT."
             <199506201242.IAA09685@combs.salem.ge.com> 
Date: Tue, 20 Jun 1995 14:48:34 +0100
Message-ID: <13626.803656114@whisker.internet-eireann.ie>
From: "Jordan K. Hubbard" <jkh@freebsd.org>
Sender: bugs-owner@freebsd.org
Precedence: bulk

> 	2)	Using the ST31200, I couldn't get it to accept the 
> 		untranslated geometry.  The system has ONLY FreeBSD on it

Yeah, we're going to be working on this more in the future.  Known
problem, and it's a sticky one.

> 	3)	BIN Dist failed to install.  DEBUG Screen said "gunzip: 
> 		unexpeced EOF" (not exact message).  Then "cpio: unexpected
> 		EOF".  Re-Downloaded new bin dist and tried again (same
> 		problem).  System was up enough to continue install.

This is weird.  How are you installing?  Over ftp?  From which site?
I've had a couple of people report symptoms like this (which I'm
utterly unable to reproduce) which leads me to believe that perhaps
one of our mirrors has a bogus dist.

> 	4)	Usr.SBin Dist failed to install with the same message as 
> 		BIN Dist.  After getting this series of messages, I tried

Ditto.  Can't reproduce at all.

> 	5)	XF86 Failed completely to install via the sysinstall 
> 		system.  I was able to extract it using the command

See above.. :-(

> 	This message is not intended to be a bitch, gripe, etc... about
> the install process.  I happen to think (once I've/You've figured out
> what happened) that the install is the best yet!  Beats the old 386BSD 0.1

Thanks, though I'd still like to know why you (and a couple of other
folks) are having such a hard time extracting these dists!  They all
work just fine for me and all the testers hanging around Walnut Creek
CDROM..

The only known bug is that /usr/src/bin doesn't extract as part of
the src dist, and that's been fixed.

						Jordan