>Number:         3771
>Category:       port-i386
>Synopsis:       boot program could give better error message
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Jun 22 07:35:00 1997
>Last-Modified:
>Originator:     Havard Eidnes
>Organization:
	SINTEF RUNIT
>Release:        NetBSD-current Jun 16 1997
>Environment:
System: NetBSD vader.runit.sintef.no 1.2G NetBSD 1.2G (VADER) #2: Mon Jun 16 21:58:48 MEST 1997 he@vader.runit.sintef.no:/usr/src/sys/arch/i386/compile/VADER i386


>Description:
	During boot when the boot program doesn't find a file, it says

	boot: No such file or directory

	This can be confusing.  Is it the "boot" file which is missing,
	or is the boot program complaining that some (unspecified) file
	is missing?  The answer is "the latter", and I propose that the
	error message be clarified by adding the file name which it's
	complaining about to the output.

>How-To-Repeat:
	Use e.g. the new single-diskette 1.2G boot diskette.
	See that boot says

	booting fd0a:netbsd

	boot: No such file or directory

	(because the kernel is gzipped, and is named netbsd.gz, which it
	finds on the next try).

	To the relative novice, it isn't clear that the "booting" message
	comes from the boot program itself...

>Fix:
	I suggest modifying bootit() in /sys/arch/i386/stand/biosboot/main.c
	in the obvious way so that it would say

	boot: netbsd: No such file or directory

	instead.
>Audit-Trail:
>Unformatted: