From nobody  Wed Jan  1 00:32:38 1997
Received: (from nobody@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id AAA18786;
          Wed, 1 Jan 1997 00:32:38 -0800 (PST)
Message-Id: <199701010832.AAA18786@freefall.freebsd.org>
Date: Wed, 1 Jan 1997 00:32:38 -0800 (PST)
From: andrew@ugh.net.au
To: freebsd-gnats-submit@freebsd.org
Subject: sysinstall: corrupt file causes restart
X-Send-Pr-Version: www-1.0

>Number:         2348
>Category:       misc
>Synopsis:       sysinstall: corrupt file causes restart
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan  1 00:40:00 PST 1997
>Closed-Date:    Wed Jan 1 01:26:03 PST 1997
>Last-Modified:  Wed Jan  1 01:28:52 PST 1997
>Originator:     Andrew Stevenson
>Release:        2.2-BETA
>Organization:
>Environment:
FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49
1996	jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386
>Description:
When installing from floppies if one of the files in corrupt (I guess
this is why it happens) it complains that it isnt a real gzip file or
something and makes you restart the whole installation. I tend to get a
better transfer rate out of my modem than my floppy drive so it can be
quite harrowing :-)
>How-To-Repeat:
Do a floppy install with a corrupt file.
>Fix:
Perhaps you could make so you just have to replace that file and continue from where you
left off.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Wed Jan 1 01:26:03 PST 1997 
State-Changed-Why:  
I'm afraid that this isn't a bug so much as a pre-requisite of 
sysinstall - you either have good media or you're hosed, and with 
the way the tarballs are split into pieces, simply skipping one 
really isn't an option.  If one piece is bad, the whole distribution 
is effectively toast and there's really not a lot I can do about it. 

This will all be solved as a side-effect of going to a more robust 
distribution archive format, so there's not much point in leaving 
this PR open as it won't be solved by fixing sysinstall in that 
way (sorry). 

There's been talking of reviving the automated checksumming, which would 
at least verify the media before starting.  I will look into this. 
>Unformatted:
