Subject: bin/4550: sysinst doesn't deal with abort/restart well..
To: None <gnats-bugs@gnats.netbsd.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
List: netbsd-bugs
Date: 11/20/1997 20:32:03
>Number:         4550
>Category:       bin
>Synopsis:       sysinst doesn't deal with abort/restart well..
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 20 12:35:06 1997
>Last-Modified:
>Originator:     Bill Sommerfeld
>Organization:
	
>Release:        971114-ish
>Environment:
	
System: NetBSD orchard.arlington.ma.us 1.3_ALPHA NetBSD 1.3_ALPHA (ORCHARD) #12: Sat Nov 8 09:13:50 EST 1997 sommerfeld@stack.ch.apollo.hp.com:/usr/sommerfeld/NetBSD-1.3/src/sys/arch/i386/compile/ORCHARD i386


>Description:
	if you abort sysinst after it mounts the local filesystems,
	and then restart it and try to pick up where you left off with an
	upgrade install, it gets confused when it fails to mount
	the disks which were left mounted when sysinst exited.
>How-To-Repeat:
	see one of my previous pr's for ways to get backed into a corner, then
	restart sysinst and watch it get confused.

>Fix:
	the code which mounts the filesystems should notice if they're already
	correctly mounted and not complain about this..

>Audit-Trail:
>Unformatted: