>Number:         7607
>Category:       install
>Synopsis:       1.4 sysinst user interface and feature set has some annoyances.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue May 18 22:35:01 1999
>Last-Modified:
>Originator:     Chris G. Demetriou
>Organization:
Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html
Disclaimer: Not speaking for NetBSD, just expressing my own opinion.
>Release:        NetBSD 1.4
>Environment:
System: NetBSD speedy 1.4 NetBSD 1.4 (SPEEDY) #18: Tue May 18 12:17:14 PDT 1999 cgd@speedy:/a/users/cgd/proj/netbsd/src-1-4-branch/sys/arch/i386/compile/SPEEDY i386

>Description:
	As always, using sysinst to try to install 1.4 (on i386) showed some
	... annoyances in the user interface and feature set.

	* yes/no menus use a & b as selection letters.  This is broken.
	It should be y & n.  (If this is an issue for other languages, then
	that should be solved, but the behaviour as-is is losing.)

	* at any, or at least most, places, ESC should get you out of what
	you're currently doing.  In the case of general selection from
	menus, that means "back to the previous menu," or perhaps "up a
	level of menus."  In many cases, it's impossible to stop doing
	things once you start.  (e.g. when installing sets, you can get 
	out of it by selecting 'none' for media on which the sets live, but
	that's not very intuitive.)

	* when populating the hard disk file system with installation
	binaries, there's junk (|s) on the right side of the screen.

	* when trying to install or reinstall sets (from the top-level
	menu item), it would appear that i have no choice but to (re)install
	the base and etc sets.  Unfortunately, if the reason why i'm trying
	to use that option is to work around the fact that, e.g. 'upgrade'
	fell right over, i might not want to install the etc set.
	Users should be able to disable it (and base).

	* (again for the case where upgrade fell over) it would be useful
	if there were options to direct sysinst to do various 'common'
	operations, such as upgrading boot blocks, and doing whatever
	disklabel upgrades are necessary for the architecture.  These
	should be independent options in case some of them cause sysinst
	to crash, or in case the user only wants to do some subset of them.

>How-To-Repeat:
	use sysinst.

>Fix:
	none supplied.
>Audit-Trail:
>Unformatted: