From owner-freebsd-bugs  Mon Nov 10 15:40:04 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA08120
          for bugs-outgoing; Mon, 10 Nov 1997 15:40:04 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA08095;
          Mon, 10 Nov 1997 15:40:02 -0800 (PST)
          (envelope-from gnats)
Resent-Date: Mon, 10 Nov 1997 15:40:02 -0800 (PST)
Resent-Message-Id: <199711102340.PAA08095@hub.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, anthony@pinkworks.com
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA08011;
          Mon, 10 Nov 1997 15:39:11 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199711102339.PAA08011@hub.freebsd.org>
Date: Mon, 10 Nov 1997 15:39:11 -0800 (PST)
From: anthony@pinkworks.com
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: misc/4999: Entering '?' at first boot prompt in installation puts system into loop
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         4999
>Category:       misc
>Synopsis:       Entering '?' at first boot prompt in installation puts system into loop
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 10 15:40:01 PST 1997
>Last-Modified:
>Originator:     Anthony J Wright
>Organization:
Pinkworks Ltd
>Release:        2.2.5
>Environment:
>Description:
As a new user to Free BSD, I was a little unsure as to the installation
process. As a result I entered '?<CR>' at the 'boot:' prompt. This gave
me a list of files, but three seconds later, attempted a boot with an
invalid boot file name, which obviously failed. Three seconds after that
it tried again and so on...

I think after getting user input it should not attempt an auto boot, 
and in response to a '?' it should not change the default kernel name.

>How-To-Repeat:
Create a 2.2.5 installation disk.
enter '?<CR>' at the 'boot: ' prompt
>Fix:

>Audit-Trail:
>Unformatted: