>Number:         3888
>Category:       bin
>Synopsis:       bogon in sh's 'type' when absolute-path'd file isn't there
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 19 02:05:01 1997
>Last-Modified:
>Originator:     Chris Demetriou
>Organization:
>Release:        'sh' from NetBSD-current as of July 19, 1997
>Environment:
System: NetBSD mother.nas.nasa.gov 1.2G NetBSD 1.2G (MOTHER) #31: Wed Jul 9 18:16:00 PDT 1997 mjacob@mother.nas.nasa.gov:/users/mjacob/isp2100/sys/arch/alpha/compile/MOTHER alpha


>Description:
	when the sh 'type' builtin is asked about the type of a file
	given with an absolute path name, and that file isn't there, it
	spits out bogus information.

>How-To-Repeat:
	run sh
	say 'type' on a file that isn't there, e.g.
	"type /usr/gnu/cc"

	For me, on alpha and i386, that gives results like:

	72 [mother] cgd % sh
	$ type /usr/gnu/cc
	/usr/gnu/cc is /usr/sbin//usr/gnu/cc

	or:

	211 [brick] mkdep % sh
	$ type /usr/gnu/cc
	/usr/gnu/cc is /usr/bin//usr/gnu/cc

	(neither of which is correct 8-)

>Fix:
	?
>Audit-Trail:
>Unformatted: