Subject: bin/4550: sysinst doesn't deal with abort/restart well..
To: None <email@example.com>
From: Bill Sommerfeld <firstname.lastname@example.org>
Date: 11/20/1997 20:32:03
>Synopsis: sysinst doesn't deal with abort/restart well..
>Responsible: bin-bug-people (Utility Bug People)
>Arrival-Date: Thu Nov 20 12:35:06 1997
>Originator: Bill Sommerfeld
System: NetBSD orchard.arlington.ma.us 1.3_ALPHA NetBSD 1.3_ALPHA (ORCHARD) #12: Sat Nov 8 09:13:50 EST 1997 email@example.com:/usr/sommerfeld/NetBSD-1.3/src/sys/arch/i386/compile/ORCHARD i386
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.
see one of my previous pr's for ways to get backed into a corner, then
restart sysinst and watch it get confused.
the code which mounts the filesystems should notice if they're already
correctly mounted and not complain about this..