>Number:         22434
>Category:       install
>Synopsis:       sysinst should not bail if xsets missing
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    install-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 11 07:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Simon J. Gerraty
>Release:        NetBSD 1.6.1_STABLE
>Organization:
Zen Programming...
>Environment:
	
	
System: NetBSD void.crufty.net 1.6.1_STABLE NetBSD 1.6.1_STABLE (CRUFTY) #1: Sat Aug 9 20:35:44 PDT 2003 root@void.crufty.net:/j/obj/sys/compile/CRUFTY i386
Architecture: i386
Machine: i386
>Description:
	
I've been bitten by this before when installing a snapshot on i386 at
least...  you go through the sysinst menus and select full install...
all goes well but the snapshot lacks the xsets.

sysinst reports that not all sets were installed and that the install
has been aborted.  The box is not bootable - at least not without a lot
of mess, because the next steps that sysinst would have done (making devices
etc) are rather important.

sysinst should either - note that the sets that did not install are not
critical and offer to continue, or at least ask the user if they should
continue.

Currently, the only solution I've found is to reboot off the floppies and
do it all again, but this time not selecting "full install".  This is
far from optimal ;-)

>How-To-Repeat:
	
Install a snapshot that lacks xsets.  Ask for full install... hose your box.

>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted: