From nobody  Mon Nov 10 15:39:11 1997
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
Subject: Entering '?' at first boot prompt in installation puts system into loop
X-Send-Pr-Version: www-1.0

>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:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 10 15:40:01 PST 1997
>Closed-Date:    Mon Jan 18 12:37:40 PST 1999
>Last-Modified:  Mon Jan 18 12:39:31 PST 1999
>Originator:     Anthony J Wright
>Release:        2.2.5
>Organization:
Pinkworks Ltd
>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:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: rnordier 
State-Changed-When: Mon Jan 18 12:37:40 PST 1999 
State-Changed-Why:  
This problem is fixed in the new bootblocks. 
>Unformatted:
